feat: add support for custom entry point#2863
Conversation
# Conflicts: # apps/dokploy/drizzle/meta/0117_snapshot.json # apps/dokploy/drizzle/meta/_journal.json
# Conflicts: # apps/dokploy/drizzle/meta/0119_snapshot.json # apps/dokploy/drizzle/meta/_journal.json
# Conflicts: # apps/dokploy/drizzle/meta/0120_snapshot.json # apps/dokploy/drizzle/meta/_journal.json
… migration - Deleted the SQL script `0122_sleepy_aqueduct.sql` which added a `customEntrypoint` column to the `domain` table. - Removed the corresponding journal entry from `_journal.json` to clean up migration history. - Deleted the snapshot file `0122_snapshot.json` as it is no longer needed.
- Introduced a new SQL migration script `0130_abandoned_dagger.sql` to add the `customEntrypoint` column to the `domain` table. - Updated the journal entry in `_journal.json` to reflect this new migration. - Created a snapshot file `0130_snapshot.json` to capture the current state of the database schema after this migration.
Siumauricio
left a comment
Siumauricio
left a comment
There was a problem hiding this comment.
Just to understand, using a custom entrypoint basically we will not add the web-secure router even if we select https?
Exactly. When custom entry-point is specified, no additional endpoints will be created. HTTPS toggle will just specify if SSL certificate should be provided |
…e/custom-entrypoint # Conflicts: # apps/dokploy/drizzle/meta/0130_snapshot.json # apps/dokploy/drizzle/meta/_journal.json
# Conflicts: # apps/dokploy/drizzle/meta/0131_snapshot.json # apps/dokploy/drizzle/meta/_journal.json
Can you create test on this case, also if you can add some docs about this here https://github.com/Dokploy/website |
There are already test cases added, that are ensuring:
Regarding docs, I will add user guide on custom entrypoint feature. Once docs update pull request will be ready I will attach link to it here |
|
Let me know when the PR is created in the website repo https://github.com/Dokploy/website |
@Siumauricio, related docs PR is created. Dokploy/website#107 |
dosubot
bot
added
the
size:L
- Implemented tests to verify the addition of stripPath and internalPath middlewares for custom entrypoints. - Ensured correct path prefixing in router rules and combined middleware functionality. - Added checks to confirm that redirect-to-https is not added for custom entrypoints even when HTTPS is enabled. - Enhanced tests for router configuration with custom entrypoints, including path handling and TLS settings.
…efik utilities - Updated conditional checks for customEntrypoint to use a more concise syntax. - Ensured consistent handling of HTTPS configurations across domain management functions. - Improved code readability and maintainability by streamlining logic in addDomainToCompose and manageDomain functions.
2 participants
What is this PR about?
This PR will allow to configure custom Traefik entry point for applications domains, by manually entering name of Traefik entrypoint. That will prevent creating default entrypoints ("web" and/or "websecure") and only will use one, that is provided.
Checklist
Before submitting this PR, please make sure that:
canarybranch.Issues related (if applicable)
closes #2851
Screenshots (if applica