If you have:
Development Environment
- Web App 1 (Separate File)
- Web App 2 (Separate File)
--Published (localhost)
--- Web App 1 (Separate File)
--- Web App 2 (Separate File)
You can have:
Server running A5 WAS - (1 IP address - 1 WAS License)
- Published (www.WebApp1.com)
--- Web App 1
or
Server running A5 WAS - (2 IP address)
- 1st WAS and (1st WAS License bound to 1st IP address)
--- Published (www.WebApp1.com)
----- Web App 1
- 2nd WAS and (2nd WAS License bound to 1st IP address)
--- Published (www.WebApp1.com)
----- Web App 1
or
Server running A5 WAS - (1 IP address - 1 WAS License)
- Published (www.WebApp1.com)
--- Web App 1
Server running A5 WAS - (1 IP address - 1 WAS License)
- Published (www.WebApp2.com)
--- Web App 2
You cannot have:
Server running A5 WAS - (1 IP address - 1 WAS License)
- Published (www.WebApp1.com)
--- Web App 1
- Published (www.WebApp2.com)
--- Web App 2
You can get pretty far in finding work arounds - running proxypass on the Apache web server, and directly manipulating links so that they are explicit. But ultimately it does not work!
Again for me this is not about bypassing licensing, but having a robust development environment where I can experiment, test, pre-deploy, and do really cool stuff. You just cannot do that within the confines of a developer workstation. You need a real server environment to do this...
To me the next version (v11) needs to have a robust developer license... Alpha is a blast to work in, except for this issue above.
If anyone has a different understanding than this -- please speak up!
Regards,
Michael Carroll
www.redrocksbluesky.com
www.theminimalistrunner.com
[email protected]
435-275-5170
Development Environment
- Web App 1 (Separate File)
- Web App 2 (Separate File)
--Published (localhost)
--- Web App 1 (Separate File)
--- Web App 2 (Separate File)
You can have:
Server running A5 WAS - (1 IP address - 1 WAS License)
- Published (www.WebApp1.com)
--- Web App 1
or
Server running A5 WAS - (2 IP address)
- 1st WAS and (1st WAS License bound to 1st IP address)
--- Published (www.WebApp1.com)
----- Web App 1
- 2nd WAS and (2nd WAS License bound to 1st IP address)
--- Published (www.WebApp1.com)
----- Web App 1
or
Server running A5 WAS - (1 IP address - 1 WAS License)
- Published (www.WebApp1.com)
--- Web App 1
Server running A5 WAS - (1 IP address - 1 WAS License)
- Published (www.WebApp2.com)
--- Web App 2
You cannot have:
Server running A5 WAS - (1 IP address - 1 WAS License)
- Published (www.WebApp1.com)
--- Web App 1
- Published (www.WebApp2.com)
--- Web App 2
You can get pretty far in finding work arounds - running proxypass on the Apache web server, and directly manipulating links so that they are explicit. But ultimately it does not work!
Again for me this is not about bypassing licensing, but having a robust development environment where I can experiment, test, pre-deploy, and do really cool stuff. You just cannot do that within the confines of a developer workstation. You need a real server environment to do this...
To me the next version (v11) needs to have a robust developer license... Alpha is a blast to work in, except for this issue above.
If anyone has a different understanding than this -- please speak up!
Regards,
Michael Carroll
www.redrocksbluesky.com
www.theminimalistrunner.com
[email protected]
435-275-5170
Comment