You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When upgrading to version v0.14.0-rc.1 of source{d} CE, I followed
the guideline on Releases section
Upgrading
For internal releases we don't support upgrading. If you have a previous sourced-ce version installed, clean up all your data before downloading this release. This will delete everything, including the UI data for dashboards, charts, users, etc:
Extract sourced binary from the release you downloaded, and move it into your bin folder to make it executable from any directory:
$ tar -xvf path/to/sourced-ce_REPLACE-VERSION_REPLACE-OS_amd64.tar.gz
$ sudo mv path/to/sourced-ce_REPLACE-OS_amd64/sourced /usr/local/bin/
However, when I tried using source{d} CE, I got an error.
$ sourced init local~/engine-srcd/repos/bblfsh
> /Users/fernandagomes/.sourced does not exist
> Cannot perform this action, source{d} needs to be initialized first with the 'init' sub command
Noticing that the folder didn't exist, I created it
$ mkdir /Users/fernandagomes/.sourced
and everything worked.
I believe there's a bug on this version, where it doesn't create this folder (~/.sourced) when the user initializes the tool.
The text was updated successfully, but these errors were encountered:
When upgrading to version v0.14.0-rc.1 of source{d} CE, I followed
Upgrading
For internal releases we don't support upgrading. If you have a previous sourced-ce version installed, clean up all your data before downloading this release. This will delete everything, including the UI data for dashboards, charts, users, etc:
sourced prune --all rm -rf ~/.sourced
On Linux or macOS
Extract sourced binary from the release you downloaded, and move it into your bin folder to make it executable from any directory:
However, when I tried using source{d} CE, I got an error.
Noticing that the folder didn't exist, I created it
$ mkdir /Users/fernandagomes/.sourced
and everything worked.
I believe there's a bug on this version, where it doesn't create this folder (~/.sourced) when the user initializes the tool.
The text was updated successfully, but these errors were encountered: