I have done a project for BE and FE (Express.js and Nuxt.js), but when it build and run it via putty on ubuntu server, this is what I get
Is that a way to make it live using Putty?
And what happens if I close Putty, will Express and Nuxt still be running on the server?
This is not a conventional way of exposing something to the Internet since it's not publicly facing the Internet (the only way right now to have access to your apps is to know the IP of the server, username + password of the SSH account).
Also, you're running the server in dev mode here, not something optimized in terms of speed.
You will need to use yarn generate (or yarn build) then yarn start on Netlify, Vercel or any platform like that for your Frontend (free service usually if using SSG).
Here is a whole list of places and how to host there for the frontend: https://nuxtjs.org/deployments
As for your backend, you may host it on Heroku, Render.com, Railway or any place of your choice (with a Node.js available).
Even a bare metal SSD can be good for such but it will require more setup overall.
Related
I need to create a local development environment and struggling a little with the setup. I want to replicate my live server as close as I possibly can.
I want to install Magento ver 2.1.8, running MySQL 5.6, PHP 7.0 with NginX and Debian.
Now, it would be more than one person which will be working on the development sites, therefore, it will have to stored on our local server.
We are working on Windows 10 Pro machines.
I had a look at tools such as VirtualBox, Vagrant and Docker but reading about them got me even more confused.
I had a brief look at the LAMP stack too. Could you recommend the best way to go for my situation?
Do I have to use these tools in combination with each other?
Do I have to install the software on each computer or on local server?
I recommend to use this docker container: https://github.com/yvoronoy/magento2docker
It uses apache but you can change it via editing Dockerfile. Main advantage in this container is configured sshfs mounting in MacOS which works a little bit faster that default mounting, and you can work with source code as you work on local instance.
Can I use Parse Server to provision service to my app that runs over intranet (a local server and multiple clients) using WLAN? If yes, how can this be achieved? if no why can't it.
No internet connection is supported yet for the app. It is designed to be used in-house only intranet via WLAN or LAN.
So far all I've seen are ways to host parse-server to one cloud infrastructure or the other.
You can easily host a parse server on your intranet.
Follow the guide and clone the parse server example
Follow the guide below (taken from the github example) for local development to get aquianted with how you set it up
Make sure you have at least Node 4.3. node --version
Clone this repo and change directory to it.
npm install
Install mongo locally using http://docs.mongodb.org/master/tutorial/install-mongodb-on-os-x/
Run mongo to connect to your database, just to make sure it's working. Once you see a mongo prompt, exit with Control-D
Run the server with: npm start
By default it will use a path of /parse for the API routes. To change this, or use older client SDKs, run export PARSE_MOUNT=/1
before launching the server.
You now have a database named "dev" that contains your Parse data
What is the best way to develop with open shift origin? Is it using vm or install it locally? I have tried installing the vm and I could not login to the vm. What is the default credential used to login to fedora vm.
Default credentials
Depending on which route you follow (see below) there might or might not be real authorization in place.
If you have the AllowAllPasswordIdentityProvider in place you can get away with test/test or whatever.
If you take the binary version (see below) this is what you'll have by default. I changed it to be HTPasswdPasswordIdentityProvider instead.
For the other options I think you will have a user called system, with the password admin coming with the setup.
Docker container version
You can quickly get OpenShift running in a Docker container using
images from Docker Hub on a Linux system. This method is supported on
Fedora, CentOS, and Red Hat Enterprise Linux (RHEL) hosts only.
Link: https://docs.openshift.org/latest/getting_started/administrators.html#running-in-a-docker-container
As per the origin folks, this setup is not (yet) a full example, but very easy to get started with. You should be able to follow the instructions to get an all-in-one instance up and running in no time. However, this approach cannot teach you how to create a cluster (master(s) and node(s))
Vagrant VM
This image is based off of OpenShift Origin and is a fully functioning
OpenShift instance with an integrated Docker registry. The intent of
this project is to allow Web developers and other interested parties
to run OpenShift V3 on their own computer. Given the way it is
configured, the VM will appear to your local machine as if it was
running somewhere off the machine.
The OpenShift Master, Node, Docker Registry, and other pieces are running in one VM. Given it's focus on application developers, it should NOT be used in production.
Link: https://www.openshift.org/vm
Binary option
Red Hat periodically publishes binaries to GitHub, which you can
download on the OpenShift Origin Releases page.
Link: https://github.com/openshift/origin/releases
This is the option I follow currently. You download the binaries, install GO, then setup the OC client tools. Next step you generate the configuration files and start adding your system components (router, ...).
Follow this page to understand the basics:
Link: https://github.com/openshift/origin/blob/master/examples/sample-app/README.md
Ansible route
For production installation you probably want to install your cluster via Ansible.
My humble advice is to do this once you got a bit of an experience via configuring by hand (see previous point). Let's hear some people with more experience though.
Link: https://docs.openshift.org/latest/install_config/install/index.html
Documentation in general
Link: https://docs.openshift.org/latest/install_config/master_node_configuration.html#creating-new-configuration-files
Spin up a Centos.7 VM, download the latest origin tools:
wget https://github.com/openshift/origin/releases/download/v1.3.0-alpha.2/openshift-origin-client-tools-v1.3.0-alpha.2-983578e-linux-64bit.tar.gz
tar xzvf openshift-origin-client-tools-v1.3.0-alpha.2-983578e-linux-64bit.tar.gz
ln -s /root/openshift-origin-client-tools-v1.3.0-alpha.2-983578e-linux-64bit/oc /usr/local/bin/oc
chmod 755 /root/openshift-origin-client-tools-v1.3.0-alpha.2-983578e-linux-64bit/oc
Bring up your single node origin cluster:
oc cluster up --use-existing-config --host-data-dir=/var/tmp/etcd
Login using the instructions provided.
I've been serving my Laravel app on my local machine (MAC OSX Maverick) via the php artisan serve command in the terminal.
How do I install it to my a free a hosting for testing? Technically, I only have a free web hosting account. This means I can't perform any command-line commands (SSH). Is there any simple way to install it? Can I just simply copy my Laravel app folder and put it on a web host?
Easiest solution: Deploy it to OpenShift using a Laravel QuickStart. OpenShift is free, gives you SSH access, and basing your app off the Laravel QuickStart should handle the more complicated configuration bits.
"Can I just simply copy my Laravel app folder and put it on a web host?"
Pretty much this is the answer. You can upload your entire Laravel application to your webserver, and it should work.
But I'll warn you now that without command-line access - your going to have issues in the future. Try and find an alternative host for your website that provides command line access
I am building worklight project using eclipse environment when i run the project , i need to connect my tablet to local network then only i works for me for all the server updates and all.
I just want to move worklight server on http server which i can access using http://publicurl/anyprject which runs on apache. Now i want to work on eclipse but whenever i deploy the project it should deploy on public so that i can access it from anywhere.
Just tell me the process and what the thing i need to move on public server.
Since you've come here to ask a question, please also take a moment to write properly structured and coherent sentences in English. This will only benefit everyone and you will get a better answer, and faster too.
Try the following:
Instead of choosing Build All and Deploy, try choosing Build for Remote Server; there you should input the external (public) IP address of your machine. Next, run the generated project in your device. This should allow it to connect to the Worklight Server.
Note that both the Worklight Server (or rather, the machine that hosts it) and the device must be on the same network, in this case - connected to the public Internet.
Based on your comment, you can:
I would seriously try to open your own machine to public access
If not possible, I would try to move to develop on the Linux machine instead
If not possible, then you must install Worklight Server on the Linux machine and whenever you make changes to the project - deploy the updated .war, .wlapp and .adapter files to your installation on the Linux machine
Build the app with Build for Remote Server so that it will connect to the Linux machine instead of the local development machine
Step 3 above means you'll need to maintain 2 development environments, which is not so easy.
If you are during development, you should aspire for options 1 or 2; in other words, create a proper development environment. In Mobile, this requires public Internet access (usually).
Are you a stand alone developer, Business Partner or a Customer of IBM?