You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Run the backend code now and it should be able to run
162
+
### Initial setup for development local environment
163
+
164
+
Step 1: Login to azure docker
165
+
166
+
The docker compose relies on images in `opensidewalksdev` azure container registry. Make sure your docker system is logged into it before pulling the images and trying to run the containers.
Use the following command to start the containers first time
177
+
178
+
`docker compose --file docker-compose.local.yml up --build`
179
+
180
+
Step 3: Run the migration scripts.
181
+
182
+
You will observe that only `osm-rails` component seems to work but the backend and other services may be down. this is because the database migrations on the base osm database are not done. To do the base migrations, do the following:
183
+
184
+
- Connect to the `osm-rails` container. If you are using docker hub for desktop, just go to the exec section of the container.
185
+
If you want to use command line, execute the command `docker exec -it <container_name_or_id> /bin/bash` where `container_name` is the name of osm-rails container
186
+
- Execute the migration script in the /bin/bash with `bundle exec rails db:migrate`
187
+
- The above command runs the migration script for databases
188
+
189
+
Step 4: Add `workspaces-tasks-local` database in postgresql
190
+
191
+
Workspaces backend relies on an additional database. This is needed for some older migrations code.
0 commit comments