How would I start doing this? I also want to maintain sessions after deploys
csisnett
danschultzer
Pow Core Team
As mentioned above, you can work it out from the Redis or ETSCache module. But is there a reason for not using Mnesia?
0
csisnett
I tried using Mnesia and a permanent disk but couldn’t change Mnesia.nonode@nohost folder where data is stored to the folder I needed
0
danschultzer
Pow Core Team
You can change it by using this config setting:
config :mnesia, dir: '/path/to/dir'
Just make sure the directory is accessible.
0
csisnett
I created a folder /mnesia in my repo and give it chmod 777
this is my config:
config :mnesia,
dir: '/mnesia'
config :pelable, :pow,
user: Pelable.Users.User,
repo: Pelable.Repo,
web_module: PelableWeb,
cache_store_backend: Pow.Store.Backend.MnesiaCache,
extensions: [PowResetPassword, PowEmailConfirmation, PowPersistentSession],
controller_callbacks: Pow.Extension.Phoenix.ControllerCallbacks,
mailer_backend: PelableWeb.PowMailer,
web_mailer_module: PelableWeb,
routes_backend: PelableWeb.Pow.Routes
but when I start the server: mix phx.server
I get the following:
** (Mix) Could not start application pelable: Pelable.Application.start(:normal, []) returned an error: shutdown: failed to start child: Pow.Store.Backend.MnesiaCache
** (EXIT) an exception was raised:
** (CaseClauseError) no case clause matching: {:aborted, {'Cannot create Mnesia dir', '/mnesia', :eacces}}
(pow) lib/pow/store/backend/mnesia_cache.ex:346: Pow.Store.Backend.MnesiaCache.change_table_copy_type/1
(pow) lib/pow/store/backend/mnesia_cache.ex:294: Pow.Store.Backend.MnesiaCache.init_cluster/1
(pow) lib/pow/store/backend/mnesia_cache.ex:125: Pow.Store.Backend.MnesiaCache.init/1
(stdlib) gen_server.erl:374: :gen_server.init_it/2
(stdlib) gen_server.erl:342: :gen_server.init_it/6
(stdlib) proc_lib.erl:249: :proc_lib.init_p_do_apply/3
0
danschultzer
Pow Core Team
Did you mean it to be relative to CWD? Then you should use ./mnesia instead. The error means that the /mnesia directory is not accessible. If it is indeed in root, then you have to ensure that the app has access to it.
0
sb8244
Author of Real-Time Phoenix
One thing I’ve done in the past is setup a free heroku Redis and then point to it from another app. 
it is free and easy to setup
1
blatyo
Conduit Core Team
You can use pow with just session cookies. Then you don’t need a store for sessions at all. The main README even mentions how to do it.
I’m using a slightly modified version of this in production. It is worth noting that password resets also use the store, so if you’re using that, you’ll have to figure out something for that.
2
csisnett
oh I didn’t know, that seems like the most straightforward of doing it
yes that’s what I meant thank you
That’s a good option as well as I wouldn’t have to pay 
0
danschultzer
Pow Core Team
For anyone coming across this thread and looking for a Postgress store, I would recommend using this: GitHub - ZennerIoT/pow_postgres_store: A Pow store implementation that uses postgres as the backend · GitHub
11