I am looking for the best practices for deploying an ExtJS app on a RHEL server. I tried installing sencha CMD on the server so that I could do the application build there, but I kept getting a segmentation fault with the 64-bit version and nothing happened with the 32-bit version (both as a normal user and with sudo). I even tried ssh'ing in with a -X option to enable Xterm, but that did not work. I am thinking I am going to have to do an external build and then deploy the entire contents to the server.
Ultimately, I would be doing this through a Bamboo server (same as Jenkins). For testing purposes though, I am going to use Webstorm. Anything I should be aware of/watch out for? I am deploying the entire project directory structure.
Alright: I was able to do this as root. Interesting. I should now be able to set up my Bamboo process.
Related
I am developing an application on .net core on my windows machine.
The app is running on a docker container with the microsoft/aspnetcore-build:2.0 image.
Everything seems fine on my computer, even when it is running in the docker container. The problem appears when it is deployed, where it is running on the same image, but on a linux instance.
for example a reference with wrong casing doesnt work.
reference: ´../Components/Car´;
actual filename: car
This will work on Windows, but not on linux.
This is because the linux file system is case-sensitive while the windows is not.
This happens for backend and frontend apps. Is there a way to circumvent this issue or find the issue earlier in the development cycle? Is there a frontend and/or backend developer tool for this stuff?
I've ran into an awkward issue. I'll try and explain this as best as I can so bare with.
I'm running Play! on a Linux VM (Oracle VirtualBox), with sbt run command in my terminal it works perfectly fine. If I use an IDE on my VM the webhook catches the change and does a reload.
I've shared a folder between my Host (Windows) and my VM (Linux) where my project directory is. I've also extended a port so that I can open my Play! web application on the Windows machine.
On my Windows Host machine I'm running an IDE (IntelliJ) and when I change something on a file, the Play! webhook running on my VM doesn't seem to pick up the changes made, even though it's listening for changes in my shared folder.
Question: Is there some sort of configuration or share folder magic
trick to get my Play! application to pick up the changes made from the
Host machine?
Thanks for reading, any help is appreciated.
inotify does not work on VMWare's shared folder. You might be able to convince SBT's filewatcher to use polling, but that doesn't work really well.
I'm building and running a .NET Core application inside a Linux-based Docker container. I'm having trouble figuring out if dotCover is cross-platform? I want to either...
Install and run dotCover inside the Docker container (that is $ dotcover analyse ...).
Or run some compatible instrumentation during the test step inside the Docker container and send a file back to the host, where I can run dotCover on the file.
Obviously, I'm already using the dotCover "server package". It doesn't indicate that it's cross-platform. So, maybe I'm stuck trying to find another way.
Resurrecting this one more time for the next reader. Jetbrains released a cross-platform console runner.
https://blog.jetbrains.com/dotnet/2019/08/26/cross-platform-dotcover-console-runner-whats-new-dotcover-2019-2/
I don't mean to resurrect an old post, but I'm going to for anyone landing on this from the internet.
Currently no, all of the ReSharper products from JetBrains are not cross platform. Windows is a requirement under the system requirements page.
https://www.jetbrains.com/resharper/download/system_requirements.html
This means that it is not readily available to run in a linux-based container or linux environment.
I have Worklight Server and Appcenter installed on RHEL 6.4 and am unable to find commands to start & stop these servers gracefully. Primarily, I would like to do this to apply patches, make changes to databases etc.. Any help is really appreciated.
It sounds to me like you are referring to installed instances of Worklight Server and Application Center in a QA/UAT/Production environment.
This means that your Worklight Server and Application Center instances are deployed to some application server (either WAS, WAS Liberty or Tomcat). So the way to start and stop these instances would be via the commands available by the the used application server. You should probably then consult with the user documentation of the used application server for the commands. For example for Liberty: http://www-01.ibm.com/support/knowledgecenter/was_beta_liberty/com.ibm.websphere.wlp.nd.multiplatform.doc/ae/twlp_admin_script.html
If you are in fact referring to the Worklight Development Server (Worklight Studio plug-in for Eclipse), there is no publically available way to stop the server from command line -- unless you are using the CLI tool to manage your development (working outside of Eclipse), there you do have a command for it.
am trying to evaluate ccnet, I have gone through a number of tutorials/blogs which describe in detail on how to install ccnet. However most of them assume that CruiseControl.NET is being installed on the same machine on which Subversion repository is or it is a server machine.
I would like to know if ccnet can be installed on a non server machine and pre - configured subversion?
Sure this is not a requirement to install CCNet on a Server nor on the same machine as your repository.
CCNet can run as console application or windows service and both can run on windows, windows server and linux/mac with Mono.
Thus CCNet uses the native applications for source control operations (e.g. svn.exe or git.exe) it also supports the same remote repository features as its source control application. So your Subversion repository can be located everywhere your CCNet machine has access to.
I recommend you to read the Scenarios Section in our wiki.
I would never install my CC.NET on the same machine as my SVN repository. But that is me.
For local testing, you can run the command line version, and not the service. It's helpful, because the Console output actually let's you pick up on a few things while it is running. (Nothing you can't find with the service, but its cool to see it "in progress").
When you do install CC.NET, I would install it on a "clean" machine. The way I like to use CC.NET is to think of it as a "big fancy msbuild wrapper".
Your CC.NET will pull code from the repository, and I like to pull the .msbuild defintion file from svn as well (meaning, you store it there), and then have cc.net use the "msbuild.exe" task. The less custom cc.net tasks you use, the better. If you put 99% of your build logic into a .msbuild file, you'll won't screw yourself if you ever leave CC.NET for TFS.
3.
Yes, it has to be able to "talk to" SVN under some Identity. This identity needs read (maybe write) rights back to SVN. But it is the identity (account) that pulls the code from SVN. If your source code is projected (most likely it will be), then you may have to do some command calls using svn.exe to "accept the (p)ermanent certificate, using the IDENTITY that runs the CC.NET service.
You'll probably have some dependencies you'll need to install. I would NOT install Visual Studio 200x or 20xx. Download and install SDK's and other things as needed. Keep the build machine "clean". Document what you install.
It is a good practices to have CC.NET running in the same environment as developer(s).
So having a standard Win7x64 OS for CC.NET is nice to reflect the dev environment.
CC.NET can be configured to access a remote or local Subversion repository depending on the svn configuration you setup.
So the answer is : yes !