# Designing a Paths Julep

**URL:** <https://discourse.julialang.org/t/designing-a-paths-julep/124335>\
**Category:** Internals & Design\
**Tags:** proposal, filesystem, path, rfc\
**Created:** [January 1, 2025, 12:37pm UTC](https://discourse.julialang.org/t/designing-a-paths-julep/124335 "2025-01-01T12:37:25Z")\
**Posts on this page:** 1\
**Showing post:** 94

<div class="post-metadata">

**Author:** ![aplavin](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/aplavin/32/222056_2.png) [@aplavin](https://discourse.julialang.org/u/aplavin)\
**Post date:** [January 13, 2025, 4:26pm UTC](https://discourse.julialang.org/t/designing-a-paths-julep/124335/94 "2025-01-13T16:26:23Z")

</div>

More generally, I skimmed through this thread but still not sure I understand the scope. Is this julep expected to accomodate stuff like remote paths?

Current Julia filesystem API makes it kinda-possible to define the Base FS interface for remotes, so that users can write functions that work with either local or remote files. But it definitely requires some care.  
One example is my package to work with [OSF.io](http://OSF.io): [GitHub - JuliaAPlavin/OpenScienceFramework.jl](https://github.com/JuliaAPlavin/OpenScienceFramework.jl).

Would be great not to lose this ability at least, and make it more principled and convenient at best.

---

_[View the full topic](https://discourse.julialang.org/t/designing-a-paths-julep/124335)._