As there is no Bitnami installer for EC2 windows servers, I started by installing the local windows bitnami installer on the windows server, but from there I am a bit stuck to get it to work.
Are there any documented steps for finalizing the configuration on a windows server ?
Also the built-in upgrade mechanism from 1.6 to 1.7.6 does not seem to work in the local windows installer from bitnami. When cliking the upgrade button, it just “erases” any content of the local index page of dreamfactory with no possibility to login again into it (blank page needing an entire reinstallation of the DSP)
ok, easy it is. A firewall rule for port 80 has to be added in the server, and it works fine.
It doesn’t solve the not functioning upgrade mechanism though, as it seems to mess things up when clicking on the green upgrade button, but I’ll wait for a new installer maybe.
When you (try to) upgrade on windows via upgrade button, it pulls dsp-core library from github and then runs the installer.sh. Unfortunately, the script isn’t yet configured to execute properly in a windows environment at this time. However, this functionality will be implemented very soon from what I have gathered from our engineers.
So, in order to upgrade on a Windows platform… there are a few steps as well as a (very small) initial learning curve. Once you’ve done this a few times, upgrading on windows is as simple as pie.
I am finishing up the official windows upgrade document as we speak. I will attach to this post shortly which will run you through everything from a to z - once you’ve gone through this process a couple times… you’re golden.
There’s a way to install using git but will only work after BitNami package is installed. Apologies for not getting that document out to you yesterday. Give me a little bit and I’ll have it to you.
Well thanks for the steps. It has updated to 1.7.6 but now there seems to be an issue, as Apache is way slower than before, and at each request, it bursts the cpu at 100% for at least 5-6 seconds…
In the admin panel, there is a gap of 5-6 seconds with the loading gear icon at each tab change too…
It seems that the update broke somethings perhaps.
When doing web/logout, also it asked for upgrading the database schema, I clicked on the green button, and now 'm wondering if the green button was not calling a bash script which would cause some issues in the windows installation like for the main dsp upgrade button.
note that the dir structure may be slightly different, as my DSP is installed as a module on top of WAMP.
[The image you are requesting does not exist or is no longer available]
When here, simply change all values = false as shown below:
[The image you are requesting does not exist or is no longer available]
Let me know if you’ve got any issues that come up.
This will turn off server side scripting functionality, but know that our engineers are already working on a solution to include in our next release to fix the speed issue without having to nix server-side scripts.
Thanks Mark, done the modification. It has a bit of speed improvement but it is still a bit laggy. I’m in a development environment so I reverted back to 1.6.10 for being sure, and it is a lot smoother in 1.6.10.
I’m happy with 1.6.10 for now for developping my apps, so I may wait until a next release to see how it behaves.
Just wondering if there will be updates to the bitnami installer for windows as well ?
I should’ve said You will need to restart apache… that is my fault, but definitely restart apache after making this change. always try to restart it after making change to your DSP.
the speed improvement is very significant - mine was close to 10x faster.
so if you’d like to try again - or if you want to do a hangout where i compare speed differences for you then just let me know
yes, did restart the apache server too, in fact i restarted both the server and mysql with the bitnami manager.
But I noticed for the todo angular example app that there was quite a delay when doing simple operations on localhost. I verified with 1.6.10 and it was a lot smoother, but i did not make any test, just using it as an end-user and there was a noticeable delay.
I may try a bit later this week to refollow all the steps you mentioned and see if the issue persists. Will post there an update for it. thanks
We are the witness of a semi-intelligent new generation robot spammer with contextual spam with semi-meaningful posts delivery backed by a comment analysis word parser.
