Best Recent Content

  • Forum guidelines

    Forum membership is exclusively linked to Enscale accounts. Our goal is to help each other grow and by combining our minds, be able to deliver the best PaaS there is so you can truly love and enjoy the Enscale experience.

    Here are some guidelines:

    • Don't be shy, if you have a question, start a thread.
    • Be respectful of others and don’t sweat the small stuff.
    • Do not post hateful or illegal content.
    • You can use private messages to chat with moderators or other members in private.

    In summary: be polite, enjoy yourself, and help us build a great community.

    pmcnano[Deleted User]
  • Environment variables per environment

    @pmcnano no problem. It was mostly with a view to keeping things as simple and straightforward as possible. If sidekiq is commonly used for cron-like functionality (i.e. as a workaround for other services not having cron), that is easiest to solve by simply using cron on Enscale!

    I'm aware of for using sidekiq in that manner.

    Your point about environment variables is a good one regardless, and of course also not unique to Ruby either.

  • Set Environment/Config variables

    I am not directly involved with the development, but yes.

    Also I understand your point and agree that this feature makes sense.

    Theoretically saving this bash profile all over the compute nodes (from file manager) would satisfy this scenario.