I have a web application that communicates to Mercurial for Clones,Pull,Push,Commit,etc and I've been using the RepositoryConfiguration.setHgrcPath to supply the [auth] username/password but need to be able to use the keyring extension instead in order to keep the credentials encrypted.
Is this currently supported by JavaHg? If so, how do I configure this to work properly?
To support your use case you don't necessarily need to use the keyring extension. For example take a look at MercurialEclipse: The files with filenames "Hg*Client.java" are examples.
But to answer your question the keyring extension is not currently supported. Take a look at some other extensions for pointers on how one would create an JavaHg extension: for example https://bitbucket.org/aragost/javahg-ext-rebase
If the keyring plugin requires configuration only then you might be better off configuring it in your .hgrc/Mercurial.ini and using JavaHg as usual
Related
I created a vscode extension for the first time..I used LSP(language server protocol) and having both client and server bundled as one extension.
The extension has highlighting and autocomplete features for a custom file type. I packaged it using vsce I got a VSIX file. I installed the extension in my vscode using the .vsix file.
The extension works when i am working on local files.
However, i connected to a remote VM using the ms-vscode-remote.remote-ssh extension such that I can view the remote files in vscode, but here my created extension is not working. I can't even see the file type i created.
Any help is appreciated. Is there some specific setting I need to put in my package.json
For your extension to properly work remotely, either installed on host or on the remote, you have to follow a few guidelines, and yes, there are some settings that you may take care of on package.json.
The first and more complete source of information is Supporting Remote Development and GitHub Codespaces API documentation. It describes the architecture, settings, how to debug, common problems and so on. There is also the Extension Host page, where it describes the Preferred extension location topic, which tells you how to configure your extension to work on the correct location.
Based on your description (a LSP related extension) I understand your extension should be a Workspace Extension. This means that you should have this on your package.json:
"extensionKind": [
"workspace"
]
The Commons Problem section describes how you can evaluate and fix Incorrect execution location. To debug using SSH follow these instructions.
Also, remember that while working with remotes, you rely on local paths anymore. Instead you must always deal with Uri, whenever possible.
I guess after reviewing your settings, based on the docs related above, you should be able to detect what is happening on your extension and fix it. Give debug a try, it will be much easier to detect issues than installing the vsix and look for erros in Console.
Hope this helps
I am newbie to TYPO3 and having a situation where I have to setup an existing TYPO3 website in my local machine so, I can make changes in some pages but the problem is that I don't have any experience with TYPO3.
What I have:
I have FTP access to the development server but don't know which folders/files are required to make it work in the local machine.
What I have tried:
I had searched regarding this on the internet and also read some past StackOverflow questions but don't find any positive response.
If someone can guide me through then it would be very helpful... Thanks!
first: you need a webserver running PHP and a database (probably mySQL).
This should match the running server.
You might use DDEV to put it all into a virtual machine and get a better match, but any webserver with PHP and mysql should do.
TYPO3 can be running in two ways:
composer mode
non composer mode
if it runs in composer mode you also need composer (and git) installed. But the copy is easier as you only need to copy the composer.lock-file and do an composer install to copy all code.
additional you need to copy all data.
that is the database.
the whole folder /fileadmin (based in webroot)
in non-composer mode you need to:
install the same TYPO3 version (typical somewhere with a symlink /typo3/ -> your location/ in the webroot.
then look for /index.php on the original server and copy it (it could be a symlink)
additional you need to copy the folder /typo3conf from the server.
and of course the data as above
then you might need to adapt /typo3conf/LocalConfiguration.php and /typo3conf/AddionalConfiguration.php. (database credentials/ domain specific info/ ...)
since TYPO3 9 you probably have a yaml config file outside the webroot.
I have the Home Assistant extension installed in VSCode but also want to use the ESPHome extension, both of these are for YAML files.
I need a way of telling VSCode which extension to use.
I wonder if it is possible to configure VSCode to use a specific extension in a specified folder tree or else to put something in the YAML file itself so the extension can recognise that it should be effective for that YAML file.
If I understand your question correct, you want to select installed extensions for in your case; YAML files.
VSCode :
Home Assistant extension
ESPHome extension
Via 'exentension' > 'dis/enabled [workspace]', you can arrange it.
Workspace recommended extensions#
A good set of extensions can make working with a particular workspace or programming language more productive and you'd often like to share this list with your team or colleagues. You can create a recommended list of extensions for a workspace with the Extensions: Configure Recommended Extensions (Workspace) command.
Extra information SEE https://github.com/Microsoft/vscode/issues/19792
This option was moved into Command pallette (F1)
Below error while uploading images for Products:
{"name":"img5.jpg", "type":"application/octet-stream","tmp_name":"C:/Windows/Temp/phpA0A2.tmp","error":0, "size"2456,"path":"C:/.../media/tmp/catalog/product","file":"/i/m/img5_2.jpg.tmp","url":"http://www.example.com/media/tmp/catlog/product/i/m/img5_2.jpg","cookie":{"name":"adminhtml","value":"ghhjgjfhghy95","lifetime":"3600":"path":"/","domain":'mysite.com'}}
I am using php 5.3 on Windows, everything else works fine.
I tried all possible ways which I know or found like giving permissions, to directories, setting c:/windows/temp on php.ini, all session variables are set to (No), I tried with User Agent (Yes) also but no success. Also mapped security settings on c:windows/temp with Media folder.
I noticed Magento not writing files on the temp directory, but i created a test file which is writing to temp dir. only Magento files are not being written?
Please anyone can support on this or any one knows some good free extension to manage product images? I prefer to have default upload working.
Magento's official system requirements (click here) show that Magento is only supported on the following operating systems:
Supported Operating Systems: Linux x86, x86-64
Try switching to a linux based development environment and see if this solves your issue.
Is it possible to keep the attributes of a version controlled file unchanged? I have a directory structure which I'd like my installer to recreate on the client machine. I was hoping the entire directory could be placed on VCS without affecting the file attributes.
I'm using TFS but would also like to hear about other version control systems.
Edit: I'm talking about Windows file system attributes such as Hidden/Archive/System/Read-only but any other information such as creation/modification dates is also welcome. I have a directory structure in which some files are read-only and need to have those files installed as such on the client's machine. TFS tends to set/unset the read-only attribute depending on whether the file is checked-in or checked-out.
TFS does not store the file attribute data (such as created date, modified date) etc in the current versions of TFS. The values for those attributes will be the time on the local computer when the files is first downloaded / modifed.
TFS 2010 has the ability to attach arbitrary metadata to version control objects. You'd have to write your own tool, however.
API specification (prelease): http://blogs.msdn.com/mrod/archive/2008/05/09/team-foundation-server-properties.aspx
Usually version control systems do not store full metadata information about the files under its control in repository. In usual usage of version control systems this is not needed, and might have even cause problems; version control systems store "sane" subset of metadata (like e.g. executable permissions, and symbolic links).
Possible solution is to use hooks to save required parts of file metadata on commit to some file (usually plain text file), keep this file under version control to distribute it automatically to all clients, and use hooks to restore metadata on checkout.
Example solutions of tools to save and restore metadata include (unfortunately examples are for Git, and not TFS, but it is the idea that matters):
metastore
git-cache-meta
Example solutions of tools to keep configuration files under version control (again: all of them using Git as a backend) include:
IsiSetup
etckeeper
giterback