Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement data movement tooling for Windows Operation Systems #191

Open
lewismc opened this issue Feb 13, 2023 · 3 comments
Open

Implement data movement tooling for Windows Operation Systems #191

lewismc opened this issue Feb 13, 2023 · 3 comments
Assignees
Labels
enhancement New feature or request

Comments

@lewismc
Copy link
Member

lewismc commented Feb 13, 2023

At todays ICCAT meeting we identified a user need which requires development of tooling to run on Windows.
Essentially, post- #189, we need to develop clientside tooling which automated data movement from a users' local directory to the staging_data directory on the server.

We may be able to use the following documentation to guide us.

Also, i requested information about client machines...

Stasha Windows 11 Pro version 21H2 OS build 22000.1455 Windows Feature Experience Pack 1000.22000.1455.0
@lewismc
Copy link
Member Author

lewismc commented Feb 28, 2023

@renato2099
Copy link
Collaborator

@lewismc Devs at ICAT seem to be using Mobaxterm for syncing files with tagserver. Do we still need to keep this issue open here?

@tagtuna
Copy link
Contributor

tagtuna commented Apr 17, 2023

@renato2099 ICCAT colleagues are happy with using MobaXterm for now, but would like to have some sort of scripting ability to "batch" import down the road if possible. It may involve a simple "cron" or "resync" user files to the staging directory onto Rackspace. Right now it is a low priority

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
No open projects
Development

No branches or pull requests

3 participants