after I deploy my package with java code changes, I can't see my changes in AEM.
To see may changes, I have to remove my old deployment package bundle from felix console, deploy my code and then restart my AEM instance to see my changes. What must be wrong ?
following are my AEM deployment steps:
mvn -Plocal-auto-deploy-with-publish clean install -Dcq.local.author.port=4502 -Dcq.local.publish.port=4503
curl -u admin:admin -F action=reset http://localhost:4502/system/console/slingjsp
curl -u admin:admin -F action=refresh http://localhost:4502/system/console/bundles/org.apache.sling.scripting.jsp
curl -u admin:admin -F action=reset http://localhost:4503/system/console/slingjsp
curl -u admin:admin -F action=refresh http://localhost:4503/system/console/bundles/org.apache.sling.scripting.jsp
If you are installing a bundle with same version (without snapshot) apache sling jcr installer will treat it as same and will not install. you will have to keep increasing the version or use a snapshot version so jcr installer knows its not final.
If your are on aem version earlier than aem 6.2, you may also want to check /system/sling/installer/pauseInstallation and delete any entries for your bundle there.
I was facing the same issue in 6.2 . What fixed it for me was when you "Import from server" in Eclipse from CRXDe the install folder also gets imported (If you have it configured within the ui.apps project) you are syncing your ui.Apps or ui.Content from CrxDe .Try deleting the install folder that gets synced too.
Also don't forget checking for extra nodes under /system/sling/installer/pauseInstallation
There are hotfixes and CFP available which works for many but in my scenario those didn't work. If it works for you well and good.
Related
i want to use REST from aerospike because its said language agnostic, im using Ubuntu 20. im trying to understand intallation part here :
https://github.com/aerospike/aerospike-rest-gateway
https://github.com/aerospike/aerospike-rest-gateway/blob/master/docs/installation-and-config.md
but its soo unclear what to do first and they jumps to "./gradlew build" at start. i put mindlessly to terminal its show like this, totally no clue
# ./gradlew build
bash: ./gradlew: No such file or directory
There are a few ways to run the REST Gateway.
You can clone the repo's master branch and build it yourself. You can then run the jar file as shown in the readme.
make build
java -jar build/libs/aerospike-rest-gateway-<VERSION>.jar --aerospike.restclient.hostname=<aerospike-host>
Download the already built jar from the download page or download it using
wget https://download.aerospike.com/artifacts/aerospike-client-rest/<VERSION>/aerospike-client-rest-<VERSION>.tgz
Untar the archive
tar -xzf aerospike-client-rest-<VERSION>.tgz
Run the jar
java -jar aerospike-client-rest-2.0.1/as-rest-client-<VERSION>.jar --aerospike.restclient.hostname=<aerospike-host>
Use docker:
docker run -itd --rm -p 8080:8080 --name AS_Rest1 -e aerospike_restclient_hostname=<aerospike-host> aeropsike/aerospike-rest-gateway:latest
Note 1: These examples assume security is disabled.
Note 2: The REST client was recently renamed the REST Gateway, which is the reason for the differing artifact names.
As far as why ./gradlew build is not running, it is a bit hard to tell. Running ./gradlew build assumes you cloned the repo and the repo is your current working directory. If you provide more info about your CWD and the steps you have followed up to this point I can help further.
I'm facing difficulties installing the MongoDB community server on Manjaro Linux.
There isn't official documentation on how to install it on Arch-based systems and Pacman can't find it in the AUR repos.
Has anyone ever tried to install it?
Here is what I did to install.
As the package is not available in the official Arch repositories and can't be installed using pacman, you need to follow a few steps to install it.
First, you need to get the URL for the repo of prebuilt binaries from AUR. It can be found here and by the time of writing this it was https://aur.archlinux.org/mongodb-bin.git
Simply clone the repo in your home directory or anywhere else. Do git clone https://aur.archlinux.org/mongodb-bin.git, then head to the cloned directory, cd mongodb-bin.
Now, all you need to do is to run makepkg -si command to make the package. the -s flag will handle the dependencies for you and the -i flag will install the package.
After makepkg finishes its execution, don't forget to start mongodb.service. Run systemctl start mongodb and if needed enable it with systemctl enable mongodb.
Type mongo in the terminal and if the Mongo Shell runs you are all set.
Later edit (8.2.2021): This package is now available in AUR.
It is available in AUR, so you can view it with pamac with -a flag,
eg.
pamac search -a mongodb-bin
pamac info -a mongodb-bin
And, then build and install with (this can be done after manually cloning too) -
pamac build mongodb-bin
Note that there's also a package named mongodb, but mongodb-bin is a newer release (you can check the version numbers by search or info arguments)
I've been using mongodb via docker for a couple of years.
In my experience, it's easier than installing the regular way. (assuming you already have docker installed)
1. Ensure you have docker installed
If you don't already have it, you can install via pacman/pamac, because it's in the official Arch/Manjaro package repositories. The easiest way is to run the following command:
sudo pacman -S docker
2. Run a single docker command
sudo docker run -d -p 27017:27017 -v ~/mongodb_data:/data/db mongo
This command will run mongodb on a port 27017, and place its data files into a folder ~/mongodb_data.
If you're running this command for the first time, it will also download all the required files.
Now you're successfully running a local instance of mongodb, and you can connect it with your favorite db management tool or from your code.
I have spun up a VM and I am trying to login to my concourse server with the following:
Christoher:pipeline christopher$ fly --target chris login --team-name chris --concourse-url http://ld4370.mycompany.com
Then, I am receiving this message:
WARNING:
fly version (2.5.0) is out of sync with the target (2.4.0). to sync up, run the following:
fly -t chris sync
However, when I do the following, I get this issue:
Christoher:pipeline christopher$ fly -t chris sync
error: unknown target: chris
At first, I had an older version of fly. So I deleted fly in my /usr/local/bin directory and then downloaded the latest. Now I am ahead of the concourse version that I installed on my VM. I have taken a look at the fly documentation but have not figured out how to get around this.
As an immediate fix to your problem, you can download any version of fly from github https://github.com/concourse/concourse/releases.
Download concourse & fly new version 5.0.0 on Mac do the following:
Download the latest version from concourse website https://mockersf.github.io/docs/download.html
then open finder press CMD + Shift + .
it will make all your hidden files visible temporarily open your user/local/bin folder then drag the new version of concourse to the bin and click replace
do the same for the fly and now go in command line press fly --version and you should see the new version
Download/ update concourse and fly version 4 and below 4 Hi go to this website basically you need to install the relevant version https://gist.github.com/kevin-smets/f20afd45a24ab3f88d01b2049ce7744f
for example:
copy this command
curl -Lo fly https://github.com/concourse/concourse/releases/download/2.5.0/fly_darwin_amd64 && chmod +x fly && mv fly /usr/local/bin/
and changed the version v2.6.0 to v2.5.0 past it in the terminal and same goes for the below :
curl -Lo concourse
https://github.com/concourse/concourse/releases/download/v2.4.0/concourse_darwin_amd64 && chmod +x concourse && mv concourse /usr/local/bin
and it should work.
I had similar problem i wanted install the v4.2.2 and it worked. the idea is the get the same version
This is similar to this question with one exception. I want to remove a few specific versions of the package from our local pypi index, which I had uploaded with the following command in the past.
python setup.py sdist upload -r <index_name>
Any ideas?
As an addenum from #jan-vlcinsky's answer
Removing from pypiserver
Using curl for instance:
curl --form ":action=remove_pkg" --form "name=<package_name>" --form "version=<version>" <pypiserver_url>
Removing packages from local pypi index depends on type of pypi index you use.
removing package from devpi index
devpi allows removing packages only from so called volatile indexes. Non-volatile are "release like" indexes and removing from them is not allowed (as you would surprise users depending on released package).
E.g. for package pysober version 0.2.0:
$ devpi remove -y pysober==0.2.0
removing package from public pypi
is described in the answer you already refered to.
removing package from other indexes
Can vary, but in many cases you can manually delete the files (with proper care).
I'm using pypiserver and had to remove a bad package so I just SSH'd in and removed the bad packages and restarted the service.
The commands were roughly:
ssh root#pypiserver
cd ~pypiserver/pypiserver/packages
rm bad-package*
systemctl restart pypiserver.service
That seemed to work fine for me, and you can just remove what you need using standard shell commands. Just be sure to restart the process so it refreshes its index.
This is my first time using Magento. I upgraded this site from 1.4.1.1 to 1.4.2.0 without issue. Now trying to go to 1.5.0.1 it just seems to refuse at every turn. I tried by entering this key into Magento Connect:
magento-core/Mage_All_Latest
And it says this:
Ignoring installed package magento-core/Mage_All_Latest
Nothing to install
I tried to upgrade via SSH and got this:
Attempting to discover channel "magento-core"...
unknown channel "magento-core" in "magento-core/Mage_All_Latest"
invalid package name/package file "magento-core/Mage_All_Latest"
Cannot initialize 'magento-core/Mage_All_Latest', invalid or missing package file
Package "magento-core/Mage_All_Latest" is not valid
install failed
In the downloader I noticed a the downloader had a version 1.5.0.0 upgrade available. I thought maybe I needed the newest downloader before I could update all the packages. I upgraded just the downloader to 1.5.0.0 which worked. Then I tried the full upgrade again and now it is mega retarded with this:
Couldn't resolve host 'magento-core'
That’s cute isn't it? So I gave it once last whirl at the ssh console and i get this bad boy:
Attempting to discover channel "magento-core"...
Attempting fallback to https instead of http on channel "magento-core"...
unknown channel "magento-core" in "magento-core/Mage_All_Latest"
invalid package name/package file "magento-core/Mage_All_Latest"
install failed
I tried a forcing it via SSH but still no love. I reverted from a backup I made so I do not have downloader 1.5.0.0 any more. Now of course I am back to square one with it telling me there is nothing to install when I try to update via MC.
When I check in MC if there are any updates available it lists these two:
Mage_All_Latest Upgrade to 1.4.2.1 (stable) Metapackage for latest Magento 1.4 release
And the Mage Downloader 1.5.0.1 but I already installed these before and it did no good so I restored my backup before the failed update.
I was trying to ask this question Magento's Forums but they are a mess right now. Their captcha fails and threads close on their own so you get little to no help. I wouldn't be surprised if they did this on purpose in concert with their 1.5.0.1 release.
Go to the root of your website and execute these commands (Where index.php is):
wget http://www.magentocommerce.com/downloads/assets/1.5.0.1/magento-1.5.0.1.tar.gz
tar -zxvf magento-1.5.0.1.tar.gz
Skip the next 4 commands if you have your magento install in a folder called Magento:
cd magento
cp -rf * /home/bitscom/public_html
cd ../
rm -rf magento
rm magento-1.5.0.1.tar.gz
For a detailed explanation see my post on the offical magento forum: here My name is Veracious on there.
If your SSH account is anything other than your apache user (i.e.: root. you will get error 500 when trying to access the site do the the permissions on the new files you just extracted. To resolve that use chown and chgrp. For a detailed explanation once again see my post:
here
I think the location for the upgrades have changed. Instead of the:
magento-core/Mage_All_Latest
use:
community/Mage_All_Latest
As what mrdon has mentioned.
I couldn't upgrade through Magento Connect either. I followed these instructions for installing magento and it worked fairly well. I changed line 3 as below to copy the folders/files over my existing ones.
wget http://www.magentocommerce.com/downloads/assets/1.5.0.1/magento-1.5.0.1.tar.gz
tar -zxvf magento-1.5.0.1.tar.gz
cp magento/* magento/.htaccess .
chmod -R o+w media var
chmod o+w app/etc
I followed the instructions from the following post to upgrade from 1.4.1.1 to 1.5.0.1:
http://www.magentocommerce.com/boards/viewthread/219720/#t301761
Then flushed the cache and reindexed everything. Everything worked.
Don't forget to change magento folder ownership to your web server user. In my case I had to run
chown -R www-data:www-data /var/www/magento