CODEWITHSUNDEEP
haskellyesod
Ecognium
Ecognium

Reputation: 2076

Deployed Keter App Logs Users Out With a New Keter Bundle

Keter has been awesome so far. For my little toy project, I used to create the keter bundle on the production server and push it keter's incoming directory and everything worked fine.

Now I wanted to learn how to setup a staging environment and so I tried compiling my bundle on staging server (it is an image copy of the production server). When I push this bundle to my production server (via scp), it logs out signed-in users. The app itself is fine after logging back in.

What has changed:

What am I doing wrong? Why does Keter care where my .keter bundle was created? Is there a way to create these bundles without disrupting signed-in users?

Thanks!

Upvotes: 1

Views: 101

Answers (1)

Michael Snoyman
Michael Snoyman

Reputation: 31315

Most likely, the issue is that a new client_session_key file is being created each time your app is being deployed. Instead, you need to generate a key file once and reuse it. This is generally handled correctly by the Yesod scaffolded site, but providing an implementation of makeSessionBackend that stores the key file in config.

What is your current implementation of makeSessionBackend? And do your keter bundles include a file config/client_session_key.aes?

Upvotes: 1

Related Questions