by Apollia - [https://apollia.com/](https://apollia.com/)
Works in Lighthouse 64 Puppy Linux 6.02 Beta 2. [http://astroblahhh.com/blog/puppy-linux/lhpup-org-is-down-but-lighthouse-64-puppy-linux-6-02-beta-2-is-still-available-i-400.shtml#blogtoc](http://astroblahhh.com/blog/puppy-linux/lhpup-org-is-down-but-lighthouse-64-puppy-linux-6-02-beta-2-is-still-available-i-400.shtml#blogtoc)
And hopefully other Puppy Linuxes that I haven't yet tried it with.
WARNING: Storing files in a RAM disk can be quite risky, such as if your computer is a desktop computer
which could instantly get turned off by a power outage, or if your laptop is running out of battery power!
If you're working on something important that you can't risk losing, it is much safer to keep it
on a physical disk instead of a RAM disk.
Ramize = installing things into a RAM disk.
Physave = saving things onto a physical disk.<br><br>
Any folder containing the "Ramize-Physave" folder can easily be ramized to whatever location in the Puppy Linux RAM disk
you want, and easily physaved back onto the physical disk it originally came from.
If Ramize-Physave and Minimal Ramize-Physave are installed in /root/apbin/ and symlinked to from the appropriate
locations in there - it is even possible to ramize a physaved folder which doesn't have its own copy of
"Ramize-Physave" or "Minimal Ramize-Physave" stored inside it.
(The advantage of storing a full-fledged copy of Ramize-Physave inside a folder is so Ramize-Physave will still work
even if there isn't a copy of Ramize-Physave installed inside /root/apbin/.)<br><br>
I made this because I sometimes prefer to edit files inside the Puppy Linux RAM disk rather than on a physical disk.
Usually because I prefer to avoid making my physical disks do unnecessary work.
Also, it used to be a nuisance for me to have to create pairs of rsync-running Bash scripts just so I could ramize
and physave whatever folders.
Now, instead, I can just add Ramize-Physave (or Minimal Ramize-Physave) to those folders. Or just run the
"Ramize Any Physaved Folder" script on whatever physaved folder I want.<br><br>
For one of my most important ramized folders, I even added a keyboard shortcut to Openbox which instantly runs
that folder's "Physave" script.
<!-- Physave apmaps -->
I expect Ramize-Physave will also be quite useful in my not-yet-finished renovated Puppy Linux Setup Kit, since
Ramize-Physave provides an easy way to install whatever folder I want wherever I want it in the Puppy Linux
<br>Sept. 12, 2018. Finally, I made a convenient action list GUI window, which will appear if you open the Ramize-Physave folder or Minimal Ramize-Physave folder with the Rox-Filer file manager.
The list contains these 6 actions:
<br>Go to Ramize Path
<br>Go to Physave Path
<br>Open config folder of [name of folder containing Ramize-Physave]
<br>Open [name of folder containing Ramize-Physave] Folder
<br>I also made a tool to easily update existing copies of Ramize-Physave: "Update dragdropped Minimal Ramize-Physave folder". It has a dragdrop GUI, but also accepts folderpaths as command line arguments.
<br>And, I added an "Update apbin copy" script, to make it easier to update my /root/apbin copy of Ramize-Physave with whatever new stuff I added to my workspace copy of Ramize-Physave.
<br>May 13, 2018. Nothing important - just changed the wording of the headers printed by some of the old installer scripts.
<br>May 3, 2018. To make Ramize-Physave more compatible with APSK Apphoard Manager - https://github.com/Apollia/APSK-Apphoard-Manager - the symlink to the folder containing the default version of Ramize-Physave is now named "Default-Version".
However, to avoid breaking a lot of old Ramize-Physave-related scripts and symlinks I still have, the installer installs the deprecated "In Use" and "Selected-Version" symlinks also.
I decided to keep Ramize-Physave's installer, so APSK Apphoard Manager won't be needed to install or use Ramize-Physave, and also because I recently decided to make Ramize-Physave one of the first things APSK (Apollia's Puppy Linux Setup Kit) installs and runs.
<br>Also, this version doesn't have an official number at the moment - it just has a version name, "Official". This is because I so frequently ended up changing things very soon after a new version number update that it probably makes more sense not to even assign a version number until I'm far more sure I'm done making changes for a while.
But, I think maybe I prefer referring to things by dates rather than version number. For example, I tend to think of my most up to date modified version of VUE - https://github.com/Apollia/VUE - as "the Feb. 23, 2017 version", since that's close to when I last worked on VUE's actual code (Feb. 22, 2017). On and after Feb. 23, 2017, all I did was edit the readme, etc.
<br>Feb. 24, 2018. Had to change the symlinks in Minimal Ramize-Physave to launcher scripts, because otherwise, they didn't work right when clicking on them in VUE: Visual Understanding Environment. http://github.com/Apollia/VUE
Renamed the app folder's "In Use" symlink to "Selected-Version".
<br>Jan. 12, 2018. Now Physave Paths must have a minimum of 2 slashes instead of a minimum of 3. (I changed this because I wanted to ramize a path which had only 2 slashes.)
And added some slight changes I forgot to upload before related to the installers.
<br>Version 1.4 - August 11, 2017. Renamed "Ramize Any Physaved Folder" to "Ramphyze Any Physaved Folder".
And added a new script, "Ramphyze Any Ramized Folder".
"Ramphyzing" is the act of making one ramized folder and one physaved folder
into a Ramize-Physave-able pair, by placing a copy of Ramize-Physave inside
the ramized folder, and automatically editing that Ramize-Physave's config files
to use the paired folders' paths.
That makes it so it's not necessary to store copies of Ramize-Physave or
Minimal Ramize-Physave inside physaved folders you want to ramize.
Various other small changes, like no longer putting stuff inside
<br>Version 1.2 - July 18, 2017. The valichecker for rsync config files is now in a separate library file which gets sourced by "Initialize Ramize or Physave".
Did that because ReplicatorBeam needs to use the same code.<br><br>
<br>Version 1.1.1 - June 29, 2017. Fixed small problems:
* In the valicheck for rsync config files, fixed a mistaken regex and added a forgotten bit containing another regex.
* And fixed "Ramize Any Physaved Folder" so it no longer makes the temporary Ramize Rsync config file invalid (a problem which caused Ramize to abort before ramizing anything).
<br>Version 1.1 - June 28, 2017. Now Ramize-Physave checks to make sure the rsync config files "Ramize Rsync" and "Physave Rsync" are valid and contain only comments and an rsync command line.