[REQUEST] A more streamlined approach to customising a Railway deployment
Maintainer antworten meist innerhalb von 1 Tag
@cameri arbeitet bereits daran.
Seit 30.11.2023.
Bewertung
Dieses Issue wurde noch nicht bewertet.
Beschreibung
Pledge
If this feature request is implemented or resolved to my satisfaction, I am willing to make a small monetary donation to support the continued development and independence of this project. Please let me know the wallet address or provide a Lightning invoice once the feature is complete.
Is your feature request related to a problem? Please describe.
I'm experiencing challenges with customising the Railway deployment in the current setup of the repository. Specifically the need to maintain custom versions of two files (Dockerfile.railwayapp and .railwayapp/settings.yaml) for my deployment needs. The current repository structure and update process (including CI/CD and lintcommit demands) make it cumbersome to maintain these customisations, especially when syncing with upstream changes. Each time there's an update, I find myself having to manually check and ensure that my customisations aren't overwritten, which is time-consuming and prone to errors.
Describe the solution you'd like
I would greatly appreciate a more streamlined approach to customising the Railway deployment. Ideally, a solution where specific files (in my case, Dockerfile.railwayapp and .railwayapp/settings.yaml) can be easily marked or configured to avoid automatic updates from the upstream repository. This would allow for more flexibility and ease in maintaining a custom setup without the risk of losing custom changes on syncing with upstream.
Describe alternatives you've considered
After reading a number of issues regarding Railway deployment, I have been able to successfully correct, customise and deploy a working, charging, instance, but future maintenance looks possibly daunting.
I've looked into various workarounds, including:
Manually monitoring the upstream repository for changes and selectively applying updates.
Attempting to use Git features like sparse checkout or branching strategies, but these are complex and not ideal for my level of familiarity with Git.
However, these alternatives are either too complex or too time-consuming for my needs.
Additional context
The ability to customise specific aspects of the deployment for platforms like Railway, is crucial to encourage a wider range of users who might wish to constrain the default wide-open settings. Simplifying this process would not only help me but potentially benefit many others in the community facing similar challenges.
- Vorherrschende Sprache
- TypeScript
- Sterne
- 829
- Forks
- 234
- Ø Merge
- 4 T. 5 Std.
- Gemergte PRs (30 T.)
- 22
Entwicklungsumgebung
- Enthält ein Dockerfile oder eine Docker-Compose-Datei
- Hat eine Pull-Request-Vorlage
- Beitragsleitfaden lesen
Erste Schritte
- Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
- Forken Sie das Repository und arbeiten Sie in einem Branch.
- Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.
Mehr aus cameri/nostream
-
validateSettings() doesn't validate rateLimits[].period — zero period silently degrades to a 1ms backoff hintEvtl. vergeben Ein verknüpfter Pull Request ist offen oder bereits gemergt. Offen
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 82/100
cameri/nostream#811 · 1 Kommentar ·
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 72/100
Maintainer antworten meist innerhalb von 1 Tag
-
feat(nip77): negentropy reconciliation core for the PostgreSQL backendEvtl. vergeben @Priyanshubhartistm hat das vor 2 Tagen übernommen. Offenenhancement
cameri/nostream#801 · 1 zugewiesene Person ·
Maintainer antworten meist innerhalb von 1 Tag
-
feat(admin): bounded NIP-66 probe history and Network Health timelineEvtl. vergeben @Ferryx349 hat das vor 3 Tagen übernommen. OffenAdmin Console enhancement
cameri/nostream#800 · 1 zugewiesene Person ·
Maintainer antworten meist innerhalb von 1 Tag
-
Store relay settings overrides in PostgreSQL (SETTINGS_BACKEND=db)Evtl. vergeben @Ferryx349 hat das vor 36 Tagen übernommen. Offenenhancement
cameri/nostream#757 · 1 zugewiesene Person ·
Maintainer antworten meist innerhalb von 1 Tag
Alle Issues in cameri/nostream
Ähnliche Issues
-
Table: Space fires onActivate in single-selection mode — the reference doc and the JSDoc disagreeOffen
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 68/100
sidorares/react-x11-components#764 ·
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 76/100
backnotprop/plannotator#1840 ·
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 78/100
JoviDeCroock/pracht#432 ·
Maintainer antworten meist innerhalb von 1 Tag
-
Add: CNN en Espanol SDOffenapproved check:passed streams:add
Schwierigkeit 1/5 Unter einer Stunde Anfängerfreundlichkeit 75/100
Maintainer antworten meist innerhalb von 1 Tag
-
Hardware attribute name "app Connection Support" has inconsistent casingEvtl. vergeben Ein verknüpfter Pull Request ist offen oder bereits gemergt. Offen
Schwierigkeit 1/5 Unter einer Stunde Anfängerfreundlichkeit 88/100
walletbeat/walletbeat#1628 ·
Maintainer antworten meist innerhalb von 1 Tag