![]() I mean, it can’t possibly be the plan to have a progress bar that’s hidden from the user unless it’s at 100% - or a system with deployment profiles that does save some parts but not all. In both cases it seems there has alway been made some effort to implement this, but it isn’t working the way it should. This makes deploying (a part of) the project quite a hassle, especially if you’ve got to do a lot of deployment because something isn’t working because of production server specific behaviour (which is out of the scope of control of Scriptcase). Remember that the API must have the same name used in the development environment so that applications can use them. Therefore, it is necessary to configure the API in the production environment during the deployment. Having useable deployment profiles now I still have to manually input all of the (S)FTP credentials on every deployment. When publishing the project, the API data configured in the development environment within Scriptcase is not sent. Generation: Last Source Code Generation date. Friendly URL: Friendly URL for the application. Like, there is a progress bar - but it doesn’t show progression or even show up at all until it’s done. Here you have an editable grid with some suitable options from your applications, such as follows: Application: Application’s Name. Even more so because after it’s done it’ll dump a finished progress bar at 100%. ZIP file that in the apl folder there are. I tried exporting the project and then importing it it looks fine in Scriptcase but when I deploy they are still there. All I had to do was wait it out but since Scriptcase provides no feedback on the UI that it’s actually doing something it was confusing. I am launching the production Project Ive been working on and noticed that the Deploy zip file includes old applications that I have deleted. The first few times I actually had to restart my development server because I though the system crashed. ![]() Once a deployment option has been chosen and Scriptcase starts to work on it provide real-time visual feedback on what it is doing. ![]() ![]() ZIP file, deploying to an external (S)FTP server is pretty much a shot in the dark weather or not PHP will throw a time-out. Even for small projects, this is easily 2-3 minutes when depoying to a. But, currently it’s just clicking a button without any visual feedback whatsoever and waiting until the browser tells you it’s done. We must inform the absolute path to the deployment directory. Deploys the project in the informed directory. Now, I can sort of understand why the entire Scriptcase system is more or less frozen during rendering - as it would make a mess if you’d be able to change files while the system is rendering their sources. The file ZIP or Tar.Gz generated, must be decompressed only in the deployment server, to avoid that the files be corrupted. Deployment could do with a few upgrades that would make the whole process much more useful and/or “ hidden magic on the background”. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |