We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Add a migration to ensure docker compose aliases consistency. Having a package name example.dnp.dappnode.eth the aliases should be:
example.dnp.dappnode.eth
example.dappnode
service1.example.dappnode
mainservice
The text was updated successfully, but these errors were encountered:
As discused today @pablomendezroyo @dsimog01 , we should change alias rules to:
For dnp packages ( example.dnp.dappnode.eth). Whether it's a mono or multi-service package:
dnp
<service_name>.example.dappnode
For public packages ( example.public.dappnode.eth). Whether it's a mono or multi-service package:
public
example.public.dappnode.eth
<service_name>.example.public.dappnode
example.public.dappnode
Is this correct?
Sorry, something went wrong.
@Marketen thats correct!
Completed
Marketen
Successfully merging a pull request may close this issue.
Add a migration to ensure docker compose aliases consistency.
Having a package name
example.dnp.dappnode.eth
the aliases should be:example.dappnode
if the package is mono serviceservice1.example.dappnode
if the package is multiserviceservice1.example.dappnode
andexample.dappnode
if the package is multiservice and has in manifestmainservice
The text was updated successfully, but these errors were encountered: