I'm hoping to really start digging into erlyweb this week, so expect 
more and more questions :)

So far I have these:

*1. .beam only deployment
*
Is it possible to deploy an Erlyweb application only as a set of 
compiled .beam files? Currently Erlyweb requires a recompile every time 
YAWS is restarted, which leads me to the next question:

*2. Startup script

*How do you handle Server/YAWS/MySQL restarts? Currently you need to 
call an erlydb:start and then an erlyweb:compile when Yaws is restarted. 
How do you automate this? How would you handle MySQL connect failures?

*3. Weird setup questions
*
I want to make a crazy setup on my site. I want to make all URLs as 
memorable as possible. So, instead of a 
http://site/article/article_title I want to have 
http://site/article_title. This is easy - just return an ewc tuple from 
hook/1.

However, there's the backend, user profiles and so on. I want to move 
them off to subdomains. For instance, I want http://profile.site.com/ to 
call the index method of the profile controller. That is, make 
http://site.com/profile/user_id work as http://profile.site.com/user_id.

How would you set up such a thing?


Thank you in advance.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"erlyweb" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/erlyweb?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to