Aurelia on shared hosting - aurelia

I was wondering if it is possible to run an Aurelia project on a shared hosting where there's no access to ssh, no NodeJS (and of course no gulp watch or anything else) with only PHP available.

I was wondering if it is possible to run an Aurelia project on a
shared hosting where there's no access to ssh?
SSH has nothing to do with Aurelia. SSH is for remotely logging in to another computer.
I was wondering if it is possible to run an Aurelia project on a
shared hosting where there's no access to no NodeJS?
Node.js has nothing to do with Aurelia. Node.js is a JavaScript runtime environment designed for asynchronous eventing within network applications. Aurelia is a client side environment that may optionally talk with a Node.js enabled server to retrieve server side data.
I was wondering if it is possible to run an Aurelia project on a
shared hosting where there's no access to gulp?
Gulp is essentially a task runner to automate things such as the minification of CSS and JavaScript files; the bundling of files; basically the repetative and tedious tasks you would perform by hand to prepare your web application for production (amongst other things).
I was wondering if it is possible to run an Aurelia project on a
shared hosting with only PHP available?
PHP has nothing to do with Aurelia. PHP is a server side scripting language designed for web development that can be used to server up information to the web client. Aurelia is a client side environment that may optionally talk with PHP to retrieve server side data.
What about ES6 / Typscript?
Aurelia, Angular 2, plain old JavaScript, etc... all can be written in ECMA 2016 or TypeScript. The transpiler, i.e., Babel or the TypeScript transpiler, will convert the code into ECMA 2015 to be compliant with today's browsers.
I'd recommend reading the Aurelia documentation, playing with the sample Aurelia skeletons, and maybe even viewing the 2 Aurelia courses on PluralSight which do a great job at introducing the Aurelia framework as well as most of the questions you've posed.

Yes it is possible. Aurelia is pure javascript and requires no server side technology to run. However, you would probably want some way to feed your Aurelia models with data from your back-end. PHP is as good a choice as any.

Related

How do I deploy a ktor project to a hostgator site?

I'm starting to learn server side development that doesn't involve my old acquaintance PHP. I have kotlin experience from Android development and am looking to leverage that using ktor for my app's server side. I can find all sorts of tutorials in getting a ktor project set up and tested locally. What I can't find are any steps in how one would get it uploaded onto my web host (hostgator).
I'll take any route needed, from building a war to dancing around a fire and chanting. ;)

Using Electron based app as a web server

I'm developing a cross-platform application (Windows/Linux/macOS), which:
Should be able to run locally as a desktop application
Should be able to run on a remote machine, preferably with the same UI as on local.
So far Electron looks good enough for the first bullet.
The question is about the second one. I'd like to reuse both the logic and the UI from the local scenario for the remote scenario. In other words, I'd like to use Electron based application as a web server and connect to it via browser.
Is there any way to do that?
You can create a remote web server without Electron, just with Node.js, and deliver a web page like a PHP server for example.
But if you want to deliver a complete remote UI and manage the window remotely, that's VERY complicated to do... That needs to configure a lot of things and manage connections between client and server, using asynchronous keyboard & mouse and encryption to secure the communications.
You want a hybrid app I think, like a few of them that out out there (i.e. Slack). Generally there's a web app plus an Electron client version with some shared UI code but it's not Electron all around. The main point of electron is to be a local web server acting as a desktop app. You could certainly keep it all node though.

Cross platform desktop development

I would like to develop a cross platform (Linux/Windows) desktop service.
This service needs to run a local HTTP server and needs to have access to a local DB.
It doesn't have any GUI components though.
Also I need to be able to create an installer for both Linux and Windows.
What is the best language/framework/SDK to build such service ?
Java could be perfect for this but I'm not sure there is a decent installer builder out there.
10x
Gilad
Have you considered the Dlib C++ Library found at http://dlib.net/? It includes "A simple HTTP server object you can use to embed a web server into your applications."
As for an installer, perhaps you should consult the following resource: http://en.wikipedia.org/wiki/List_of_installation_software#Cross-platform.

Publish an web application on build with NAnt, MSBuild or any other tool

I have a scenario where I have to setup a test environment where I want to be able to tell my NAnt or other build tool to make an new IIS web application, put the latest bins in the newly created IIS web application, and post me an email where the new address and port where the new application are addressed, is this possible and how? which tool?
There are several ways to approach this:
Set up a continuous integration (CI) server on the test environment. This is a viable option if your test environment machine doesn't change often and it's a single machine.
Push the installation from your development machine using tools like PsExec
Combination of the two: you have a build CI server which pushes the installation to (multiple) test environments.
Of course, you also need a good build script which will set up the IIS application (NAnt offers tasks for this). Emailing to you can be done by CI server (CruiseControl.NET Email Publisher, Hudson...).
I suggest taking some time to read this excellent article series: Automation for the people: Deployment-automation patterns
Our CruiseControl .Net build server does exactly this as part of it's NAnt build-script process...
Once the code is retrieved from source control, it's all built/compiled in turn. Web projects are then handled slightly differently to normal .dlls, as they are deployed to a particular folder (either on the current machine or otherwise) where IIS (also set-up by the script) to serve the pages.
Admittedly, we're using Virtual Directories instead of creating and disposing of new website instances on the server, as otherwise we'd have to manage the port numbers for each website.
NAnt has the capabilities of doing all of this IIS work, as well as all of the email work too - I'd certainly recommend looking at this avenue of enquiry to solve your problem. Plus, you also get the continous integration aspect as a side-benefit in your case!

How to separate development of client-side web UI and the server side

I'm in the process of providing a Web UI as an alternative to our current desktop UI for our C/S enterprise application.
When developing the client-side in our desktop version, UI developers could connect to any server so they only needed the client-side environment.
When developing a Web UI (Client-side JavaScript in the browser), we are bound by the browser's "Same origin policy" so the UI must talk to the same server from which the UI code is downloaded.
As far as I see it till now, the development scenario for the UI guys is:
Developer installs server on local
machine and runs it.
Developer edits the HTML+JS+CSS files on local installation.
Developer has to reinstall/update server on local machine each time there's a need to test UI code against new server behaviour.
This does not seem too comfortable, at least compared to our previous C/S style development.
Are there any other ways you can suggest to that will not require UI developers from installing and updating server side components on their development machine ?
Or anything else related that can simplify the development process ?
Thanks :-)
Editing in some clarifications:
I'm mostly interested in the aspects of UI coding, not UI design.
I need a lot of server interaction - getting data from RESTful web services, which are developed in parrallel - hence the need to have an up-to-date server
You haven't specified the development platform.
As far as pure HTML/JS/CSS is concerned, you don't need a server. The UI developer can fine tune UI components locally.
The moment you want to talk/integrate to Server (via AJAX, JSP, ASP...) then you need to connect a development server as now your changes have to be served by Server.
Most of UI fine tuning can also be done from Firebug
In our office when changes to styling are required we save the page as a local copy and send it to the UI designer, he makes his changes and we integrate them. So the UI designer don't have to maintain a development environment.
JSONP lets you work around the same-origin problem (with server support) -- check it out! If the front-end-in-the-browser developers are using a good framework suc as jQuery or (my favorite) Dojo, JSONP should be no harder for them than plain JSON.
Develop on a shared server, but depending on the size of the team.. that's challeging with respect to version control.
Or deploy automatically generated virtual machines with nightly builds, so the devs don't have to install, but always use a recent version.
In the case of UI developers depending on a common REST server, the UI development can be done on the local machine and the REST service should be on a central server. When changes are made to the REST service these should be deployed to the central server (when stable), so all developers can use the newest version (this also helps with testdata).
You could try using a proxy on the developer's machine where some paths redirect to the server and some paths redirect to local folders.
Hmm, I actually didn't really get any information on what kind of technology you're using. If - with UI Developers - you mean designers, which have to take care about the CSS, layout etc, then we do it the same as lud0h said. We (developers) send the UI designers a copy of the server-side produced HTML pages. They then edit the HTML pages according to accessibility guidelines, CSS and layout and send us back the outcome of their work. We use their HTML pages then for integrating them in our web applications.
If you don't just mean tuning CSS, but also to write JavaScript / Ajax functionality you HAVE to use a server with which you're communicating. As you said, normally this is done by having a local environment which is similar to the server-one. In .Net Visual Studio '08 provides an internal webserver, alternatively you have to install IIS locally. In Java environments you have to install Tomcat and related technologies. In my eyes this is a must. What you have to have is
Versioning system (CVS, SVN,...) where developers commit regularly (minutes/hours)
local environments where developers checkout the source from the repository and develop
Test server where you deploy on a daily basis (could be like daily builds) in order to test your running product
I guess this should be what a professional development environment should consist of. The difference to C/S application development is that web UI and web-client code are not that separable as a Client UI in C/S environment from the server-side. Unless you develop with technologies like GWT or Silverlight which are quite similar to C/S, just running inside the browser, but communicating over RPC calls or web services.
//Edit:
What I nearly forgot. Don't do something like developing on the server directly, meaning that all of the developers access the server's filesystem where the code, UI etc. lies!!
You can use CORS. a new technique just like Ajax, but with ability to make calls on other domains. so you will need only one UI on one server. think this can help you.