New post
Announcement
· Nov 28

[Video] Boost Your Productivity with Command History & Shell Aliases in InterSystems IRIS

#Video #InterSystems IRIS

Hi Community,

Enjoy the new video on InterSystems Developers YouTube:

⏯ Boost Your Productivity with Command History & Shell Aliases in InterSystems IRIS

https://www.youtube.com/embed/R1W9f0w8n7s
[This is an embedded link, but you cannot view embedded content directly on the site because you have declined the cookies necessary to access it. To view embedded content, you would need to accept all cookies in your Cookies Settings]

Discover how to quickly access command history and use shell aliases like :py and :sql to streamline your workflow. Save time, rerun commands effortlessly, and enhance your development efficiency!

🗣  Presenter: @Ash Sherzhanov, Solutions Administrator, Data Center, InterSystems  

Enjoy watching, and expect to see more videos! 👍

Discussion (2)3
Log in or sign up to continue
Ash Sherzhanov · Dec 11

Hi @Alexander Pettitt, great question! The pre-defined aliases, like :py, :sql, and :history, are built into the system I believe. Custom aliases, yes, they come from the ~/.iris_init file, which is user-specific and located in the user's home directory.

To make aliases instance-specific, the only workaround I’m aware of is to use separate system users for each IRIS instance, each with its own .iris_init file. Unfortunately, I don’t believe there’s a native way to directly tie aliases to a specific instance unless this user-level separation is implemented.

Let me know if you’ve explored other approaches!

Regards,
Ash

0 0