Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Updating ISLE docs #1797

Merged
merged 17 commits into from
Jul 23, 2021
Merged

Updating ISLE docs #1797

merged 17 commits into from
Jul 23, 2021

Conversation

dannylamb
Copy link
Contributor

Purpose / why

More accurate install docs, plus actual instructions for upgrading/updating.

What changes were made?

Filled in the gaps on https://islandora.github.io/documentation/installation/docker-compose/ and then some.

Verification

Please try as much of this stuff as you can.

Interested Parties

@Islandora/8-x-committers @Islandora/documentation


Checklist

Pull-request reviewer should ensure the following

  • Does this PR link to related issues?
  • Does the proposed documentation align with the Islandora Documentation Style Guide?
  • Are the changes accurate, useful, free of typos, etc?
  • Does this PR update the last updated on date on the documentation page?

Person merging should ensure the following

  • Does mkdocs still build successfully? (This is indicated by TravisCI passing. To test locally, and see warnings, see How To Build Documentation.)
  • If pages are renamed or removed, have all internal links to those pages been fixed?
  • If pages are added, have they been linked to or placed in the menu?
  • Did the PR receive at least one approval from a committer, and all issues raised have been addressed?


### Config Import

`make config-import` will export import site's configuration from your site's config sync directory.
Copy link
Member

@bseeger bseeger Apr 14, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

will export import site's should probably say will import site's

Should this also point out where the config/sync directory is? namely, it's in config/sync in your drupal's www folder - describing roughly where that location is.


- Used `make demo`
- Are using a custom Drupal image
- Don't want to bother with setting up a development environmen right now
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

type on word environmen

@dannylamb
Copy link
Contributor Author

Thanks for the feedback @bseeger ! Done!

docs/installation/docker-compose.md Outdated Show resolved Hide resolved
docs/installation/docker-compose.md Outdated Show resolved Hide resolved
docs/installation/docker-compose.md Outdated Show resolved Hide resolved
docs/installation/docker-compose.md Outdated Show resolved Hide resolved
docs/installation/docker-compose.md Outdated Show resolved Hide resolved
```

If you do not provide a `codebase` folder before running `make local`, you will be given a vanilla Drupal 9 installation with the `islandora` module enabled and only the iminimal configuration required to run. It's not for the faint of heart, but if you want to avoid using `islandora_defaults`, you can build up your entire repository this way.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

typo, minimal.

Also, it appears the expected workflow for anyone doing "real site building" (not just kicking the tyres) starting out is to "already have a site" and I'm confused at the catch-22 here.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What would the recommendation be for a group just starting with Islandora for a production environment? As @rosiel eluded to this is confusing.

For example, we are looking to start using Islandora, but want a starting point that we can customize but not be a full blown demo site with non affiliated data. Thanks!


If you used `make local` then the drupal root folder is in a new directory in the isle-dc folder named `codebase`. This is live and editable in whatever development environment you would like. If you just did `make demo`, you will need to spin down your containers with `-v` to destroy your state before starting a new one with `make local`.
Use `docker-compose up -d` to bring a site back up. You should _not_ run `make local` or `make demo` again unless you used `-v` when shutting down the site.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So, make local and make demo should only ever be run once, unless you delete the volumes, and if changes are made to any of the docker-compose files, we should only be using the make -B docker-compose.yml command, correct?

@misilot
Copy link
Contributor

misilot commented Apr 22, 2021

Could recommendations for deployment for a Production environment be added? For example the following topics

  • Configuring the SSL certificate or be able to utilize Let's Encrypt / or specify another ACME provider?
  • Steps on how to utilize the make local for development environment, with steps to create our own containers that can be deployed in production
  • DISABLE_SYN I can't find what this is used for, but it is in the .env file.
  • ENVIRONMENT what are the valid options for this variable
  • Recommendations for what should be disabled. Should we be editing the different docker-compose files or some other method? For example there are comments of "Do not expose in production." in the different files. Just trying to understand what I should be commenting our and where.

Thanks for working on this! It was very easy to stand up, just want to make sure I am doing it correctly.

- Set `INCLUDE_CODE_SERVER_SERVICE=true` in your `.env` file
- make -B docker-compose.yml
- docker-compose up -d

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it possible to use code server with a make local install and codebase directory?

@dannylamb
Copy link
Contributor Author

I have completely rewritten massive chunks of this, restructured and re-organized them, and tried to address all the feedback I was given.

I know it's a lot, but if anyone has a chance to give this a look and give me any more feedback, I'd super appreciate it.

@mjordan
Copy link
Contributor

mjordan commented Jun 24, 2021

@dannylamb as a relative newby to ISLE and someone who has struggled a bit getting to understand it, I would be happy to review these docs.

@mjordan mjordan self-requested a review June 24, 2021 20:56
Copy link
Contributor

@mjordan mjordan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't see any documentation on how to not run a particular container. For example, if I don't want to run blazegraph, how would I configure .env (or whatever) to tell Docker to just skip deploying that container?

docs/installation/docker-prereq.md Outdated Show resolved Hide resolved
docs/installation/docker-prereq.md Show resolved Hide resolved
@rosiel
Copy link
Member

rosiel commented Jul 20, 2021

@mjordan have your changes requested been met?

@mjordan
Copy link
Contributor

mjordan commented Jul 20, 2021

@rosiel yes

@bondjimbond
Copy link

@mjordan it's still showing "changes requested"; is there a way for you to mark them as resolved?

Otherwise, is this good to go?

@mjordan
Copy link
Contributor

mjordan commented Jul 23, 2021

Sorry, changes accepted.

@bondjimbond
Copy link

Cool. So who gets to hit the merge button?

@mjordan
Copy link
Contributor

mjordan commented Jul 23, 2021

Since I was the holdout, I'll do it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants