I am in the process of migrating to the latest version of ProGet. I'm currently using version 3.8.6, so am quite far behind the stable release.
I decided to start fresh, moving to a brand new Windows Server 2016 box in AWS, and using RDS for the SQL database.
The new setup is working perfectly, I have imported our NuGet packages by creating a feed, entering a Drop Path and dropping all of the packages there. ProGet picked up on this and moved them all to the Feed.
However, I am now trying to import our npm packages. I've created the feed, added a drop location and moved all the npm packges over. On the old server, they're all already in subfolders. ProGet seems to refuse to add them unless they're in the root folder specified as the Drop Path. So I've moved some packages there (inconveniently they're all called package.tgz...) and it picks them up, moves them to /ProgramData/ProGet/Packages/.npm/F5/ puts them in folder too but then does not become visble in the feed on the web interface.
The package number increases, and if I click packages I can see them all, then click into them and download the package, but it doesn't show up on the main Feed 'Page'.
On the other hand, if I manually upload a package via the web interface, it doesn't put the packages in the same location as above, but it is visible on the main feed page... Is this a bug or am I doing something wrong? The NuGet packages work perfectly using the same method, so I'm confused as to why npm isn't working.
I noticed this same behavior when using the bulk upload utilizing the drop path. From what I can tell, you must have at least one version with the "latest" tag on the details for it to show anything in the Feeds view.
Related
I've done a bit of googling and haven't been able to find any documentation on this, but I need to upgrade my Seeddms (Document Management System) server from 5.1.25 to 6.0.19.
I am running a Linux Lamp 4.19.0-19-amd #1 SMP Debian 4.19.232-1 (2022-03-07) with a Seeddms web server on it.
I tried copying the contents of the .gz download file of the latest version over my current /var/www/html/dms/ folder and it didn't work, I did a similar thing to update my dokuwiki site so I thought I'd give it a try here.
I am still new to Linux so any advice would be greatly appreciated!
I was able to find the solution, in the seeddms-quickstart-x.x.x/seeddmsxxx/seeddms-x.x.x/doc/README.Install.md.
Here is what is says on upgrading versions if anyone has trouble with this as well. Make sure your server meets the requirement as well.
UPGRADING FROM A PREVIOUS VERSION OF SEEDDMS
As SeedDMS is a smooth continuation of LetoDMS there is no difference
in updating from LetoDMS or SeedDMS.
You have basically two choices to update SeedDMS:
you install a fresh version of SeedDMS and copy over your data and configuration
you replace the software in your current installation with a new version
The first option is less interuptive but requires to be able to set up a second
temporary SeedDMS installation, which may not be possible, e.g. because of storage
limitations. It can be the only option if you change servers.
The first update procedure is only needed if the version changes on the minor
or major version number. Changes in the subminor version number will never
include database changes and consequently it is sufficient to use the existing
data directory and database with the new version. Choose the second update
option in this case.
In both cases make sure to have a backup of your data directory, configuration
and database.
Fresh installation and take over of data
The first update option is to set up a new instance of SeedDMS and once
that is running take over the data from your current (old) instance.
just do a fresh installation somewhere on your web server and make sure it
works. It is fine to use
SQLite for it, even if your final installation uses MySQL.
replace the data directory in your new installation with the data directory
from your current installation. Depending on the size of that directory (and
whether the new installation is on a new server or the old server) you
may either copy, move or place a symbolic link. The content of the data directory
will not be changed during the update. Its even perfectly save to
browse through your documents and download them after finishing the
update. The data directory will not be modified until you actually modify
documents.
copy over the configuration settings.xml into your new installation. This will
effectively make your new installation use the data from your old installation,
because all paths are still pointing to the old installation.
if you use mysql you could as well make a copy of the database to make sure
your current database remains unchanged.
modify the settings.xml to fit the environment of the new installation.
This will mostly be the
httpRoot, the paths to the installation directory and possibly the database
connection.
create a file ENABLE_INSTALL_TOOL in the conf directory and point
your browser at http://hostname/seeddms/install
The install tool will detect the version of your current SeedDMS installation
and run the required database updates.
If you update just within the last version number (e.g. from 5.1.6 to 5.1.9),
this step
will not be required because such a subminor version update will never
contain database updates.
Upgrading your current installation
Instead of setting up a new installation, you may as well replace the php files
in your current installation with new versions from the quickstart archive.
get the SeedDMS quickstart archive seeddms-quickstart-x.y.z.tar.gz and
unpack it somewhere on your disc.
copy the directory seeddms-x.y.z from the unpacked archive into your
current installation and make the link seeddms point to this new directory.
copy the directory pear from the unpacked archive into your current
installation, replacing the existing directory. Make a backup of pear before
the replacement if you want to ensure to be able to go back to your old version.
you may compare your conf/settings.xml file with the shipped version
conf/settings.xml.template for new parameters. If you don't do it, the next
time you save the configuration the default values will be used.
create a file ENABLE_INSTALL_TOOL in the conf directory and point
your browser at http://hostname/seeddms/install
The install tool will detect the version of your current SeedDMS installation
and run the required database updates.
If you update just within the last version number (e.g. from 5.1.6 to 5.1.9),
this step
will not be required because such a subminor version update will never
contain database updates.
I'm having some troubles with a situation and I would like to get your help. I'm using CruiseControl.NET to create the packages of my builds and it creates them correctly. The package versions are beeing stored at a folder in a remote machine.
However, when I use Octopus, I set a local feed with the correct URI for that folder. The folder has the right permissions (read/write). But when I try to create a release of the package in Octopus, it can't reach the version of the package. Plus, when I test it to get the list of packages, the list is always empty. So, I don't get the version when I try to create the release.
I already tried to change the credentials for the access (using another user), and I already changed the directory. I can ping the remote machine, I can enter via remote connection with those users, and I can reach the folder in Explorer. Plus, I double checked the folder permissions... But I'm still getting the same problem. I don't know what is going on and Octopus doesn't allow me to deploy the package without a version.
I'm running Octopus 1.5.1.1652 and CruiseControl.NET 1.8.3.0.
Problem
I setup a composite c1 website on Azure using the app market place.
I installed the blog package some time ago but never used it.
I would like to remove the package but when I try to do so, I receive an error stating that the Entries.xml file can not be located and the uninstall exits.
I have manually created the Entries.xml file in my system folder, in the correct place, but I still get the same message.
Question
How can I uninstall this package that is failing to uninstall?
Any help would be appreciated.
Credit to Inna on codeplex for this answer
Hi,
Please note that Composite C1 was moved to https://github.com/Orckestra/C1-CMS
Composite C1 Packages - https://github.com/Orckestra/C1-Packages
I reported the Blog package issue here - https://github.com/Orckestra/C1-Packages/issues/15
Please try next workaround how to delete the package from the console:
1) make sure that package files are deleted form the site folder . I think that all files were deleted when you was trying to uninstall package first time, just re-check, if not, then delete.:
locate folder \App_Data\Composite\Packages\303b7865-055b-4fe7-a429-907b32bb6776
locate file uninstall.xml
make sure that files listed in node deleted from the site folder.
go to Data perspective -> Global Datatypes and make sure that datatypes with namespace "Composite.Community.Blog" deleted.
go to Layout perspective -> Page Types and make sure that Blog pagetype is deleted.
2) Delete folder \App_Data\Composite\Packages\303b7865-055b-4fe7-a429-907b32bb6776
I am trying to install a package (oForms) with a new Orchard 1.8 installation, but receiving the following error:
"Package installation failed: There was an error installing the requested package. This can happen if the server does not have write access to the '~/Modules' or '~/Themes' folder of the web site. If the site is running in shared hosted environement, adding write access to these folders sometimes needs to be done manually through the Hoster control panel. Once Themes and Modules have been installed, it is recommended to remove write access to these folders."
This seemed rather straightforward, however my host has confirmed permissions are fine (and even added Everyone/Full Control to the folder), so I'm lost and appears to be happening with all modules from the Gallery, not just oForms. I changed the Config/log4net.config file to log everything, and I don't see anything specific in there except where it logs the same message above. Nothing outside of that stands out at all.
Is there a way to see why this is failing? Or, if not, is there a way to get the module and install it manually? I tried to download from the gallery, but it's just a NuGet package so I'm not sure how to take that and grab the raw module files.
You can use a program like 7zip to unzip the nuget package, then copy in the module manually yourself.
As for the permissions, when adding a new permission to the folder use:
IIS AppPool\name of your application pool
I also had this exact error message when installing modules from the gallery, and it took me a while to figure out what was happening. I made new installations, copying over files one-by-one, and eventually found the culprit. For my case anyways...
For me, it was all due to a bad formatting in my custom Theme. Specifically the Theme.txt file. The line where is says Version:, I had it formatted without any "."
Good:
Version: 1.0
BAD:
Version: 1
Yes, doing this simple mistake prevented me from installing Modules.
I have a project that uses clickonce to generate the setup.exe. During the run time my program create some extra files like "Log" and "Attachments" inside the User Folder. However, those folders are not removed when I perform an uninstall of the clickonce application from the ARP. These remaining files are interfering the next install.
I know that click once does not support for adding custom action to install or uninstall. I am wondering if is there is a way that I can remove those extra file programmingly after performing uninstall?
One way I have tried was to create a cleanup script and added it as a bootstrapper package to pre-requisite of the click once project. That worked in a way that every time before a new product was installed, the previous dirty data had been removed. However, this messed up the upgrade case.
Any ideas on how to remove the extra files that left by clickonce uninstallation?
Thank you
JS
There is no way to do anything when uninstalling a ClickOnce application other than uninstall the ClickOnce application.
Have you considered putting the files in the ApplicationDeployment.CurrentDeployment.DataDirectory ? Then they will be removed when the application is unisntalled.
If the files are part of the project, you can set the type to Data in the Application Files dialog, and it will automatically place them in the data directory when deploying.
This solution works on multiple re-installations (clean), however it doesn't remove the data on last uninstall or until the next installation takes place.
Stil there is no custom action place on uninstall to remove the files beyond clickonce scope.
Leave a file in to ApplicationDeployment.CurrentDeployment.DataDirectory.
On startup, see if the file exists on conditions network deployed, firstrun (which resets on upgarde too).. success case, it is a first installation or upgrade. Failure case, the application is been uninstalled and installing again .. now you have a chance to clean up the application data.
If the data is sensitive, you may want to use other solution to remove files on uninstall ( as of now I don't see that Microsoft is given us an option)