So how does one take a stroll and relax, than code. Say you are than in an elevator or lobby and can code, than they go back to a desk and keep on the same script without missing a beat they keep learning code on their scripts.
Pick any language, and if it doesn’t work than just pick the next and save all of them centrally at one nice and clean place. iPad, droid, desk, Linux computer than an interviewer or bosses desk with the next use!
What You’ll Need:
- A desktop computer and phone with Termius, or a friendly copy-paste SSH client that can store keys for you to remote into.
- Google Drive, your own email account, iCloud or another secured online place for 1-3 days file storage.
- A credit card to register an Amazon Account or use your personal one.
- $3.50 a month. You have a 1 month trial by Amazon in Lightsail and if you hate my article and pay this only on month two wiht a 30 day trial. Alternatives could be an account with DigitalOcean ($5/mo) Hetzner, Linode or Vlutr.
- Maybe googling Linux commands when stuck
Step 1 – Register an Account on a Cloud Provider
I recommend Amazon Lightsail in my site as they’re awesome for price. Amazon wants a valid phone for you to verify with and the process is great if you already have a private account. Simply go to https://lightsail.aws.amazon.com and register an account if you want something both secure and innexpensive.
Amazon consumers to do this on Lightsail due to size and scope of Hardware, so iOT or other small projects are fine. You need a valid credit card and phone for verification. Nothing major or expensive, just a reliable little cloud for saving work.
Use the Linux type you wish. If reasons for learning or immersion with Linux are business related than I reccomend CentOS 7. If not, well than there’s even FreeBSD (go devils!!)
Step 2 – Generate a new SSH Key profile for the Instance.
Try never to use a cloud default ssh key. Generate a new one and save it to a secondary online site so you can get the key to each device you’re going to script on.
Step 3 – Copy the Key to your safe desktop at home, or onto your cloud for temporary storage.
So this part is important. We do not wan to keep data at risk. You use the cloud service to store the data and than login to save the keys to each system. Once saved to a long term secured storage over say 1-3 days than you need to delete the key from the cloud as it’s not at all secure.
I wouldn’t type any login account details or passwords into the source you save it in just in case a James Bond happened to break into your storage and I do not recommend Dropbox for the reason that they warn their not encrypted so employees could see your file.
Alternative – upload the key to an email in DRAFT you never email (ever ever ever) it out and than download it to each device. Doing so you still must absolutely delete it after short term storage of a day or so.
Step 4 – Setup a Virtual Interface (or static IP) and connect it to the instance.
This allows all your devices to know the password and one consistently permanent phone number but if you had to delete everything inside the instance you don’t have to completely re-setup all your devices.
If you need to wipe out the instance, you will no longer need to redo step 2 or all the devices the new key needs. For that matter you won’t need to change the phone number to get to the device either. It can be swapped out if something goes wrong and if things are backed up either with FileZilla or a snapshot, that never see that work disappear.
Step 5- confirm that the key and login credential setup works.
If the key fails or you cannot work with that device 2-3 times successfully, than you may need to repeat steps 2-3.
I recommend the app Termius as they allow really easy copy paste. If you have a background in networking, please don’t use PuTTy. That would be a huge frustration for a setup as a good copy-paste at least in lines along with color tools for showing what you’re connected to and the text colors will help you in vim, nano or eMACS.
Tip: Open a second SSH to the site and use the man command in a second Termius window when you’re stuck in a Linux computer and need to run something on a command line!
Step 6 – Go to your target book, teacher or app service and download their course materials, txt notes and scripts.
Try to get as many of them as you can collected and than run FileZilla or a compatible SFTP computer and upload all of them to your /home directory. I’d keep a disaster backup of all your files at this computer with FileZilla so that if something happens and the instance dies you save all your play scripts and work.
Step 7 (optional) – Setup GIT on your computer for file versioning.
Keep the training really basic. Google a cheat sheet online, etc. if it’s your first time using git. You could go further than this later with Jenkins and have a separate site that holds the portfolio content. Really an expactation for DevOps so you might as well tinker with it so you’re confortable.
Step 8 (optional) – Run a snapshot of the instance if you don’t mind the small cost.
You want to do this before you run Linux updates or upgrades so that you have a fall back and is very much worth a few cents if you do it and than test the updated software for a few days (or hours) before confirming and deleting your work.
Step 9 (optional) – Adjust your firewalls so that only your targeted devices will only be able to SSH to the machine.
No one should have to stress about this stuff. Keep things private and delete ports 80 and 443 than have SSH on port 20 to only a select group of IP’s.
Step 10 – Setup the connection on your phone or device.
Now no matter where you travel you have no miserable mess with reading something on a book and not having a perfect and consistent place to test and run the scripts.
Step 11 – (NOW) Build your target programs after all the books, labs and experiences you have with ease!!
Desktop/Laptop Computers: type the scripts…
Droid/iPhone on a walk: debug the scripts…
iPads: Study course or book provided scripts…
You could pull them right off git hub!
We as Americans have incredibly stupid cell phone bills. We pay tons on entertainment and utilities, yet we can for just 12 cents a day harness some time and effort with scripts and monopolize on a silent simple technology that provides for our homes and pays our bills for years.
Just remember that the effort now is upon you to use the tool. You will really really regret deleting that instance once you get into books so enjoy a library or a cheap dollar menu hamburger and take a few quality minutes each day to code.
So the following you should make text message files of and save into the server so that at a client computer if stuck you can just copy and paste the links below into your browser:
- Google Search needed configurations and commands you’ll use:
- git versioning cheat sheet
- run gittutorial
- man git
- vim commands cheat sheet:
- i, escape, :w, :wq :q!
- linux commands:
- ls, mv and so forth for copy, paste.
- git versioning cheat sheet
I save my linux commands and details in a folder titled Linux Commands and keep them handy to get used to them for your distro if you’re new to Linux. As you’re in scripts there’s not much you directly need to do in the OS. Just perform this work on a desktop for detailed work and backup the instance before or after you do it.
Stay tuned as I will have more posts on things you can do in Linux to help things along!