-
Notifications
You must be signed in to change notification settings - Fork 71
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
Updating ISLE docs #1797
Conversation
docs/installation/docker-compose.md
Outdated
|
||
### Config Import | ||
|
||
`make config-import` will export import site's configuration from your site's config sync directory. |
There was a problem hiding this comment.
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.
docs/installation/docker-compose.md
Outdated
|
||
- Used `make demo` | ||
- Are using a custom Drupal image | ||
- Don't want to bother with setting up a development environmen right now |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
type on word environmen
Thanks for the feedback @bseeger ! Done! |
docs/installation/docker-compose.md
Outdated
``` | ||
|
||
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. |
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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!
docs/installation/docker-compose.md
Outdated
|
||
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. |
There was a problem hiding this comment.
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?
Could recommendations for deployment for a Production environment be added? For example the following topics
Thanks for working on this! It was very easy to stand up, just want to make sure I am doing it correctly. |
docs/installation/docker-compose.md
Outdated
- Set `INCLUDE_CODE_SERVER_SERVICE=true` in your `.env` file | ||
- make -B docker-compose.yml | ||
- docker-compose up -d | ||
|
There was a problem hiding this comment.
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?
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. |
@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. |
There was a problem hiding this 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?
@mjordan have your changes requested been met? |
@rosiel yes |
@mjordan it's still showing "changes requested"; is there a way for you to mark them as resolved? Otherwise, is this good to go? |
Sorry, changes accepted. |
Cool. So who gets to hit the merge button? |
Since I was the holdout, I'll do it. |
Purpose / why
What changes were made?
Verification
Interested Parties
@Islandora/8-x-committers @Islandora/documentation
Checklist