synpse VS Advanced SSH config

- Docs (https://docs.synpse.net/) - what you like, what you find confusing

# Name of your app name: synpse-calendso scheduling: type: Conditional # Need to match your labels # Ref: https://docs.synpse.net/synpse-core/applications/scheduling selectors: type: controller spec: containers: - name: calendso image: ctadeu/calendso:0.0.17-1 env: - name: BASE_URL value: https://calendar.synpse.net - name: NEXTAUTH_URL value: https://calendar.synpse.net - name: DATABASE_URL fromSecret: calendsoPostgresConnString - name: CALENDSO_ENCRYPTION_KEY fromSecret: calendsoEncKey - name: GOOGLE_API_CREDENTIALS fromSecret: calendsoGoogleApiCredentials restartPolicy: {} - name: prisma image: codejamninja/prisma-studio:latest ports: - 5555:5555 env: - name: POSTGRES_URL fromSecret: calendsoPostgresConnString restartPolicy: {} - name: postgres image: postgres:latest volumes: - /data/calendso-postgres:/var/lib/postgresql/data env: - name: PGDATA value: /var/lib/postgresql/data/pgdata - name: POSTGRES_USER value: calendso - name: POSTGRES_DB value: calendso - name: POSTGRES_PASSWORD fromSecret: calendsoPostgres restartPolicy: {} # Caddy provides HTTPS - name: caddy image: caddy:latest args: - caddy - reverse-proxy - --from - calendar.synpse.net:7300 # This should be your domain and port, same as in your router - --to - calendso:3000 ports: - 7300:7300 volumes: - /data/calendso-caddy:/data - /data/calendso-caddy-cfg:/config restartPolicy: {}

docs: https://docs.synpse.net

If you have any questions or suggestions, feel free to start a new discussion in our forum or drop us a line on Discord

Yeah this is the easiest route. You could also trying something like assh which allows you more flexibility.

I'm using assh (https://github.com/moul/assh) in terminal and it is aliased to ssh, however this does not work with tramp, is there a way to define ssh path for tramp? Thanks.