I have installed the EC2-steps plugin, restarted rundeck, but I can't see the steps. Is there anything I'm missing here, installation or interface wise?
With this steps works:
1) Get the plugin with: git clone https://github.com/rundeck-plugins/aws-ec2-steps
2) Compress on .zip file with: zip -r aws-ec2-steps.zip aws-ec2-step
3) Now, move the zip file to /var/lib/rundeck/libext (DEB/RPM based installation) or $RUNDECK_BASE/libext (WAR based instllation).
4) Check the new steps available.
Tip: Check the zip file permissions, make sure that the Rundeck user (or the user that launches Rundeck) can read the zip file.
Related
There is no "check for updates" when using the standalone/no install version.
What is best way to update a standalone version without losing settings etc.?
According to my experience (VSCode in a standalone .zip file uncompressed in D:\ using Win7 OS) you just need to download and uncompress the archive containing the new version (v 1.41.1).
When you run Code.exe in the new folder, your settings file is used and everithing is OK. (then, when you are really really sure that it is everithing OK, you could delete the old version).
If you changed the default settings file location, take a look at https://code.visualstudio.com/docs/getstarted/settings#_settings-file-locations
From the official doc it says when downloaded through zip file, one has download the release manually for each update and place the unzip version inside the Program files (Windows).
According to the special portable page all the settings, plugins, etc. of the standalone version
are stored in the data-folder. So assuming you called your vscode-folder vscode:
download the new version
unpack to vscode2 folder adjacent to current vscode
move data folder from vscode to vscode2
delete old vscode-folder
rename vscode2 to vscode
done
P.S.: Current portable versions notify about new version, but clicking on it leads to download, so above list still applies.
Edit 2020/08/04: To make a "normal" install portable one just needs to create the data folder inside the installation/unpack directory of VSC.
To download the old archive, replace user|system with archive in the URL.
Before:
https://update.code.visualstudio.com/1.69.2/win32-x64-user/stable
After:
https://update.code.visualstudio.com/1.69.2/win32-x64-archive/stable
I'm hosting an AppImage file on github releases
https://github.com/Gilad-Kutiel-App/jumpfm/releases.
The file does not have an execution permission when downloaded and it is needed to set it manually.
Is there anything I can do about it ?
Thank you,
Gilad
Before you can run an AppImage (or really any executable for that matter), you need to make it executable. This is a Linux security feature. There are three main ways to make an AppImage executable:
1. With the GUI
Open your file manager and browse to the location of the AppImage
Right-click on the AppImage and click the ‘Properties’ entry
Switch to the Permissions tab and
Click the ‘Allow executing file as program’ checkbox if you are using a Nautilus-based file manager (Files, Nemo, Caja), or click the ‘Is executable’ checkbox if you are using Dolphin, or change the ‘Execute’ drop down list to ‘Anyone’ if you are using PCManFM
Close the dialog
Double-click on the AppImage file to run
2. On the command line
chmod a+x Some.Appimage
3. Automatically with the optional appimaged daemon
If you would like to have all AppImages be executable automatically, you can install the optional appimaged daemon. It will automatically add downloaded AppImages to the menu and make them executable for you. It can be downloaded from https://github.com/AppImage/AppImageKit/releases or installed from your distribution.
On your download page, you can link to the image and/or to http://discourse.appimage.org/t/how-to-make-an-appimage-executable/80
Note: Please DO NOT put an AppImage into another archive like a .zip or .tar.gz. While it may be tempting to avoid users having to set permission, this breaks desktop integration with the optional `appimaged daemon, among other things. Besides, the beauty of the AppImage format is that you never need to unpack anything
Many thanks in advance, I am using advanced installer 12.1, the scenario is we have already installed application with some custom location feature and is extends the default application location, this installation creates some folders to store temporary files like "Temporary" folder, this folder is used by the application on every minute basis and hence there are some files in this folder, now issue is when i run a new build or try to install the new version of the application, i again select the another custom location, before finishing the installation the installer deleting all the folders installed with older version but not deleting the folders which contains files created by the application e.g the temporary directory above is deleted if it is empty but when it is non-empty it is not removed.
Solution i tried:
1) I used file Removal tool to remove the file, but i think it point the current location and not pointing the older application path.
2) A custom VB script, but again the same issue as #1
3) I tried uninstall cleanup wizard, result #1
Please guide me how i can delete that folder, any help would be appreciated.
Thanks
I am unable to install the following question types with my moodle
1. Drag and drop into text (qtype_ddwtos)
2. Drag and drop matching (qtype_ddmatch)
I am using I am using Moodle 2.5.4 (Build: 20140113), php 5.4.7, MySQL 5.5.27, Apache 2.4.3, XAMPP server version 1.8.1
I have downloaded the plugins and unzip it then placed in the moodle->question->type. After that if I click the notifications link it is showing only blank page. Please advise me how to go further and how to resolve this issue and make use of those plugins.
the idea is to give the 755 permission to the "ddmatch" and "ddwtos" folders.
1- copy the two folder to moodle->question->type (as you did)
2- cd to this this directory:
cd /opt/lampp/htdocs/moodle/question/type
3- and change the permission of the two folder:
sudo chmod -R 755 ddwtos ddmatch
it worked for me !
I just checked out 2.5.4 and downloaded the plugins you mentioned - making sure they were both 2.5 versions - and extracted them into /question/type
https://moodle.org/plugins/view.php?plugin=qtype_ddmatch
https://moodle.org/plugins/view.php?plugin=qtype_ddwtos
Then went to notifications, they both require other plugins
qtype_match doesn't exist unfortunately
https://moodle.org/plugins/view.php?plugin=qtype_match
However gapselect does, so I downloaded that one too
https://moodle.org/plugins/view.php?plugin=qtype_gapselect
Then ran the upgrade and no errors were shown.
Is this on linux? Its possible that the extracted files haven't got the correct permissions - check the ownership of the folders : http://docs.moodle.org/25/en/Security_recommendations#Running_Moodle_on_a_dedicated_server
I would also double check that the files have been unzipped into the correct folder - so you should have /question/type/ddmatch, /question/type/ddwtos and /question/type/gapselect
If all that is okay then, like davosmith says, if you can switch on debugging and paste the error here. If you can't get into the system then edit /config.php and add these 2 lines after $CFG = new stdClass();
$CFG->debug = 32767;
$CFG->debugdisplay = 1;
Then try going to notifications again and see what the error is /admin/index.php
We're setting up an OpenSolaris server on Amazon's EC2 service. However, vi/vim doesn't work properly, and pkg doesn't have nano/pico.
Is there any other text-editor maybe?
Sounds like you may just need to set an appropriate termtype to get vi working. Look into the "TERM" environment variable options, perhaps one of those will help you.
You may try copying the nano binaries (or compiling the source), to your user account and running it from there. It worked for me in a similar situation.
Have you looked at http://www.sunfreeware.com/?
SUN is working on the SUNWgnu-nano package to include this in the next release. In the meantime, you can compile the nano sources yourself. It worked for me. To compile, follow these steps:
Make sure you install SUNWgcc package so that gcc is installed.
Download the source package from the debian distribution.
http://packages.debian.org/source/stable/nano
Unzip the package with 'gunzip xxxx.tar.gz' where xxxx.tar.gz is the source package you downloaded.
Untar the package with 'tar -xf xxxx' where xxxx is the unzipped source package.
Go to the source folder. Do a './configure' to create the make file for your system.
Type 'make' to create the binary
The 'nano' binary should be located in the src subfolder. Copy this to '/usr/bin'. And create a soft link for 'pico' to it i.e. 'ln -s /usr/bin/nano pico'
Test it out!
1) Open the Package Manager (System > Administration > Package Manager)
2) Open the Repository settings (Settings > Manage Repositories)
3) Add the Blastwave repository (Name: blastwave, URL: http://blastwave.network.com:10000 )
4) Select the repository in the upper right corner
5) Search for the package 'IPSnano'
6) Select the pacakge
7) Press 'Install/Update'
8) Modify your path to include /opt/csw/bin
(For example $ vi ~/.profile and then add the line above to your path)
9) Logout and in again to reflect the changes
Check whether the correct version of nano is used:
$ which nano
It looks like both Nano and Pico are available as auto-generated packages in the "pending" repository here: http://pkg.opensolaris.org/pending/en/index.shtml. I think they are waiting for someone to follow the verification steps and vouch that they work. Then they can be moved to the contrib repository. You can read more here: http://opensolaris.org/os/community/sw-porters/.