Page MenuHomePhabricator

Add directories to Files
Open, LowPublic

Description

This task describes far-future work.

Currently, Files is roughly a big list of file blobs with no structural information. A separate application, Phragment, provides a directory structure for build artifacts with some special rules, but is primarily not intended to be user-facing.

I'd like to merge Phragment into Files and provide directories within Files, so you can, e.g., create a group of files related to a particular project and organize them into a directory structure. This structure would be versioned and have some special rules to let it replace Phragment completely, but primarily work like normal directories on disk on the OS in a user-facing "folders of stuff" sort of way.

Further in the future, we could write desktop applications to do directory sync.

Event Timeline

Phragment is super out of date and FYI, hasn't seen any usage from me for a while. I don't know if anyone else is using it, but you can probably feel free to just delete the whole thing since it's a prototype anyway.

Phragment is super out of date and FYI, hasn't seen any usage from me for a while. I don't know if anyone else is using it, but you can probably feel free to just delete the whole thing since it's a prototype anyway.

I'd really like it for Herald: "Assign task to user stored in Phragment" or related type rules.

Users don't have anything to do with Phragment? Unless I'm misunderstanding something?

Users don't have anything to do with Phragment? Unless I'm misunderstanding something?

I was confusing Phlux and Phragment - ignore me.

Phlux should probably be on the chopping block too since Almanac pretty much obsoleted it in Phacility production.

I'm hesitant to axe it because Sitevars were so useful at Facebook as a flexible, general-purpose tool, but I don't currently have any use cases in mind for it that I'm particularly excited about.

Phlux should probably be on the chopping block too since Almanac pretty much obsoleted it in Phacility production.

I'm hesitant to axe it because Sitevars were so useful at Facebook as a flexible, general-purpose tool, but I don't currently have any use cases in mind for it that I'm particularly excited about.

this may not be great for this ticket, but I have a number of use cases for a phlux-like configuration. Its one way to implement a rotation. i.e., assign to the "user listed in this phlux config". Its also useful for enabling/disabling things. For example "if the emergency phlux config is set, then block pushes to the repo".

eadler added a project: Restricted Project.Aug 5 2016, 5:24 PM