Fix docker volume mappings for node_modules
, improve docker-compose usage #138
No reviewers
Labels
No Label
integration
discourse
integration
ejabberd
integration
ldap
integration
lndhub
integration
nostr
bug
design
dev environment
docs
duplicate
enhancement
feature
good first issue
idea
invalid
kredits-1
kredits-2
kredits-3
on hold
ops
question
release
major
release
minor
release
patch
security
ui/ux
wontfix
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: kosmos/akkounts#138
Loading…
Reference in New Issue
No description provided.
Delete Branch "bugfix/fix-docker-mapping"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This simplifies the
docker-compose.yml
management, by leaving it uncommented as devs can selectively start any of the services defined by name, eg.docker compose up ldap
, while new users can start up everything withdocker compose up
.Additionally, I added a mapping to the web volumes list,
/akkounts/node_modules
will excludenode_modules
from being mounted, ensuring it is defined as a docker-only directory within the mounted directory.Added
PRIMARY_DOMAIN: kosmos.org
env to both theweb
andsidekiq
docker compose directives.👍
Fix docker volume mappings for `node_modules`, leave docker-compose.yml uncommentedto Fix docker volume mappings for `node_modules`, improve docker-compose.yml usageFix docker volume mappings for `node_modules`, improve docker-compose.yml usageto Fix docker volume mappings for `node_modules`, improve docker-compose usage