mirrors/bonfire-app
1
0
Fork 0
mirror of https://github.com/bonfire-networks/bonfire-app.git synced 2024-05-15 15:42:39 +00:00
Code Issues Projects Releases Wiki Activity

schema

Browse source
This commit is contained in:
Mayel de Borniol 2021-12-12 19:01:44 +13:00
parent 8c2228fb86
commit 2a023de2a2
2 changed files with 4 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
docs/DEPLOY.md
View file

@ -99,7 +99,8 @@ Now that your tooling is set up, you have the choice of using pre-built images o
#### Option A1 - Using pre-built Docker images (recommend to start with)
- Edit the `image` entry in `docker-compose.release.yml` to reflect the image on Docker Hub which corresponds to your chosen flavour.
- The `image` entry in `docker-compose.release.yml` will by default use the image on Docker Hub which corresponds to your chosen flavour (see step 1 above for choosing your flavour).
You can see the images available per flavour, version (we currently recommend using the `latest` tag), and architecture at https://hub.docker.com/r/bonfirenetworks/bonfire/tags
- Start the docker containers with docker-compose:
@ -160,7 +161,7 @@ There is a `Makefile` with relevant commands (make sure you set the `MIX_ENV=pro
- `make rel.tag.latest` adds the "latest" tag to your last build, so that it will be used when running
- `make rel.push` if you want to push your latest build to Docker Hub
Once you've built and tagged your image, you can update the `image` name in `docker-compose.release.yml` to match (either your local image name if running on the same machine you used for the build, or a remote image on Docker Hub if you pushed it) and then follow the same steps as for option A1.
Once you've built and tagged your image, you may need to update the `image` name in `docker-compose.release.yml` to match (either your local image name if running on the same machine you used for the build, or a remote image on Docker Hub if you pushed it) and then follow the same steps as for option A1.
For production, we recommend to set up a CI workflow to automate this, for an example you can look at the one [we currently use](../github/workflows/release.yaml).

2
lib/web/graphql/schema.ex
View file

@ -93,9 +93,9 @@ defmodule Bonfire.GraphQL.Schema do
mutation do
import_fields(:common_mutations)
# Extension Modules
import_fields(:me_mutations)
import_fields(:social_mutations)
import_fields(:tag_mutations)
import_fields(:classify_mutations)